R2-Beta - Goals, Plan, Strategy (Top level objectives)

Return to Index Page
Most recent messages (500 max) are listed first.

#UserMessageDate
163OldesMaybe I'm too dareful, but if it's not a big problem, can we get a build (even unsecure) with Rebcode please? Just to make sure, that the Rebcode is not forgotten. Else I'm still using 1.3.61 version.13-Jun 10:34
162PaulI do hope we continue to evolve the 2.7.x platform.6-May 15:30
161BTiffinIf work continues to 2.7.7 (it should - the public directory litter and +s mishandling alone should be reason enough to pump out another release) how about porting the libc definition from %printf.r in rebol.org. It may not be necessary but I'd like to proactively fight platform splintering now that routine! is freed.6-May 14:28
160BrianHWe need to make sure that /Command FastCGI works with the new official FastCGI extension to IIS from Microsoft, the one written by Zend. We can probably afford to ignore other third-party FastCGI extensions to IIS on Windows from now on.14-Apr 23:51
159AntonI wouldn't go further than 1.3.21-Apr 9:50
158BrianHHow far back in versions should I continue to test? I've never tested on earlier than View 1.3.2.21-Mar 15:08
157BrianHDevBase 2 (the current platform) will be tracking the current REBOL 2 release as the primary testing platform - currently that means 2.7.6. Any new functions in R2 that DevBase is using will be duplicated in a backwards compatibility file.21-Mar 15:07
156CarlBeware the color map!19-Mar 3:50
155CarlOSX SDK uploaded to www.rebol.net. AltME uploaded here to Other folder.19-Mar 3:50
154CarlSee how it works for you. I know it works well enough to type this message and upload itself.18-Mar 23:25
153CarlAlso, uploaded here AltME for Linux based on 2.7.6. It is the Other folder.18-Mar 23:24
152CarlNew SDK for a Debian Linux has been uploaded to www.rebol.net. This can be used instead of the Fedora version (newer lib/kernel compat).18-Mar 23:24
151AntonQuickly testing my style-gallery.r seems pretty stable with rebview windows build in Wine on Kubuntu.18-Mar 15:42
150Gabrielethe current linux sdk works fine for me on Ubuntu. what was the problem with it?18-Mar 7:38
149Carlhttp://www.rebol.net/upnews/0028.html For noting compat problems.18-Mar 2:25
148CarlWaiting to hear results from view and core first.18-Mar 2:10
147CarlHave not uploaded new linux sdk yet.18-Mar 2:10
146GrahamI linux sdk I downloaded yesterday had everything?16-Mar 18:34
145CarlIt this build seems better, can make the whole SDK .16-Mar 17:35
144CarlNote that new Linux Core and View are posted. Let me know.16-Mar 17:34
143Paulsweet! Congrats to ALL!14-Mar 23:24
142CarlNote it will take a couple days to get all the OSes posted.14-Mar 22:59
141CarlThank you R2 team here, for your help, advice and contributions!14-Mar 22:59
140CarlREBOL 2.7.6 Released14-Mar 22:58
139CarlWe can do a special release for you Oldes.14-Mar 17:32
138CarlOSX changes are done.14-Mar 17:31
137OldesI don't need official rebcode version. It's working fine for me. Honestly I need it more than adding new mezzanines. And that's the reason why I still use Rebol 1.3.6114-Mar 8:21
136WillArpok, thank you13-Mar 23:42
135CarlYes. The OSX changes are still pending, so they WILL happen for 2.7.6 if possible.13-Mar 23:41
134WillArpmaybe tracker item #13 is not too complicate ?13-Mar 23:40
133CarlMerged. Holding on above. Release deadline is Friday.13-Mar 23:38
132CarlFetching DevBase change for TAKE.13-Mar 23:34
131Gabrielei'm ok with leaving it as is, unless someone can give a good reason for changing it.13-Mar 23:33
130CarlWill timeout tomorrow. If no comments, it remains as is.13-Mar 23:31
129CarlHolding release on CALLBACK issue. Waiting for discussion to finalize.13-Mar 23:31
128CarlOn RebCode - not included. Main reason is my original explanation (2006?) regarding security.13-Mar 23:30
127CarlPosted in test group. Moved to Tested status.13-Mar 23:28
126CarlTesting #10...13-Mar 23:28
125CarlOk Brent.13-Mar 23:27
124BrianHParticularly the crash-REBOL-with-ease issue :(13-Mar 22:24
123PekrI fear Rebcode was still beta, some late requests were not implemented, not sure if they were even discussed. And unless the instruction set is complete, I am not sure it is good to have it added. IIRC BrianH also mentioned its security issues ...13-Mar 22:21
122PaulI agree with Oldes, would be nice to have rebcode also.13-Mar 22:09
121BrentCarl, did you end up having to change code in the SDK for the OSX bug? If so, I don't think that was retested.13-Mar 20:40
120BrentThe only bug that I didn't get good confirmation on was #10, Win32 registry issue.13-Mar 20:39
119CarlGraham, let me do quick check on that problem.13-Mar 18:52
118Gabriele(also, let me know if you need testing on OSX PPC.)13-Mar 18:38
117GrahamIf it's too much work leave the encap header bug to 2.7.7 and release now.13-Mar 18:38
116Gabrieleno showstoppers here (assuming the color problem on osx intel gets fixed ;)13-Mar 18:38
115OldesIt seems to fine for me, just if you can do a version with rebcode as well please.13-Mar 18:35
114GrahamIs that easy enough?13-Mar 18:35
113GrahamCan we fix the encap header bug ?13-Mar 18:34
112CarlLet's get this released!13-Mar 18:32
111CarlBrent will coordinate this finalization.13-Mar 18:32
110CarlAttention everyone:

* We need to finalize 2.7.6 and get it released and out to developers. * We know that we cannot fix every bug or the release won't happen until 2010. * So, are we ready now to ship, or is there anything urgent, "show stopper" that needs to be fixed?

13-Mar 18:31
109GrahamThanks12-Mar 18:22
108CarlGraham: uploaded.12-Mar 17:48
107Grahamrebcmdview is also missing ... I can't do any testing.11-Mar 6:10
106CarlOk, so starting the wrap up for 2.7.6. Once call gets figured out, we can do OSX and Linux. OSX intel requires fix for colors. We can also make Solaris core.11-Mar 5:41
105GrahamCarl, enfacecmd is still missing from the SDK distro ...11-Mar 5:27
104CarlSo you can do any other tests. (Let me know if you need a license.key)11-Mar 4:46
103CarlSDK exe files for Win32 uploaded to releases dir.11-Mar 4:45
102Gabrielethe Win version seems good enough though. and Linux is surely not worse than 2.7.5. but, as long as we don't hold too much, that's fine.10-Mar 22:41
101Gabrieleit's just that there are more versions available to test :)10-Mar 22:40
100CarlLooks like a lot more testing going on today -- a good thing -- so we will hold release.10-Mar 22:37
99CarlNote: this is project goals group.10-Mar 19:43
98GabrieleProgram received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000504 0x00025297 in ?? () (gdb)10-Mar 19:20
97GabrieleBus error here (Leopard)10-Mar 19:19
96Gabrielecool, giving it a go.10-Mar 19:15
95CarlYes, will do some cmd builds today.10-Mar 19:15
94CarlThis is the first OSX Intel View build.10-Mar 19:15
93CarlView for OSX intel upoaded -- but note: the graphics has an endian problem -- the colors are wrong. Other than that, it should work fine.10-Mar 19:14
92GrahamCarl, would you upload rebviewcmd and enfacecmd as well... my apps use /cmd features and so to test my apps under 2.7.6 I need /cmd.10-Mar 18:07
91WillArpI could try an osx-intel build 8)10-Mar 17:51
90CarlWe are in testing and release stage now.10-Mar 17:48
89CarlI should note that 2.7.6 changes and fixes are frozen.10-Mar 17:48
88CarlUploaded review-linux - a best to try out.10-Mar 1:19
87CarlPaul, yes -- but, in mezz group.8-Mar 19:00
86CarlUploaded rebview-276b.exe -- "final beta" -- includes BrianH mezz fix.8-Mar 18:59
85PaulCarl can you discuss briefly the goals you desire for mezzanines? What your thoughts in particular concerning speed concerns - chaining mezzanines (building mezzanines on top of mezzanines), etc..8-Mar 15:47
84Henrikif he uses VMWare, he can test it all on his Macbook :-)8-Mar 14:01
83MaartenGabriele, you have too much hardware ;-)8-Mar 13:39
82GabrieleI'll be away most of today though, so I'll probably be able to test tomorrow.8-Mar 11:07
81GabrieleI can test Linux, Wine, OSX PPC, OSX Intel. I can also test Windows, but I guess there are already a lot of testers there :)8-Mar 11:05
80PekrAnyway, with R3, stuff like /odbc and /https have to be in standard ....8-Mar 9:45
79Pekrcool, thanks for shell fix and thanks for library! That could definitely make some guys happy. It opens them to use SQLite without the need for /Pro. /ODBC would be fine too for connectivity, but that is probably much to ask :-))8-Mar 9:45
78BrianHWe can fix mezz stuff at least.8-Mar 6:32
77CarlTrue in R3. (But, not so much in R2. It's limited and difficult to make various changes. For example, note that I could not fix the bug in set pair return value.)8-Mar 6:27
76BrianHFuture releases should have more stuff fixed, more cool stuff.8-Mar 6:25
75BrianHMuch as I appreciate the fixes, this release seems to me to be a trial run for a new development and release process.8-Mar 6:24
74Carl(just kidding)8-Mar 6:22
73CarlOk, so this file is for testing prior to final release. Now is the time to check it. After release, you will need to wait until 2.7.7 release in March 2010.8-Mar 6:22
72CarlCalled: rebview+mezz.exe8-Mar 6:15
71CarlPreliminary release that includes the current DevBase Mezz changes.8-Mar 6:15
70CarlMezz merged. Making new build.8-Mar 6:09
69CarlMerging mezz functions now.8-Mar 5:50
68CarlA preliminary release has been uploaded into the releases/test folder.

This is a test version prior to adding the mezzanine function change in DevBase.

*Fixes the top bugs listed in Tracker. *Removes license restriction from Library features. *Removes CALL window Win32 black console (use /show option to see it) *Adds new SHIFT function - works on integers and binary (bytes) *Control over master sound control is optional (use NONE for volume)

Use the datestamp (system/build) as a reference (it is 7-Mar-2008).

8-Mar 5:48
67PaulWin XP and Vista here.8-Mar 3:59
66PaulBrent I shoudl be available a bit tomorrow8-Mar 3:59
65BrentCalling all beta testers! If you are interested and able to test the fixes for 2.7.6 Saturday 8 March, please let me know here or in private. Thanks!8-Mar 2:42
64Carl[Reviewing tracker records now]7-Mar 18:47
63Carl(or, stated another way, lazified)7-Mar 18:42
62Carloptimized7-Mar 18:42
61BrianHfind/match7-Mar 18:41
60CarlSomething like this should work... foreach f load %./ [if find f "r2-" [rename f remove/part copy f 3]]7-Mar 18:40
59BrianHThe REBOL 2 mezzanine sources have been uploaded to DevBase, in particular the 2.7.5 SDK sources.

I had to prefix the files with r2- because DevBase currently requires filenames to be unique. This will change, so don't try to fix the file references in the source to match. Just remove the prefix before use. We should probably add a tool to do this automatically.

I also uploaded the Viewtop source (prefixed with r2-vt-) and the installer source (prefixed with r2-inst-). Same rules apply.

For now, just make your changes in these files. We can diff from them as needed.

7-Mar 7:23
58HenrikI agree4-Mar 19:48
57Gabrielei would actually limit ourselves to fixing as many bugs as we can in the available time frame. we can add new stuff for the next release. we could set it to be due for april, or may if you don't want to spend too much time on R2.4-Mar 19:47
56CarlSkipped almost a year!4-Mar 19:44
55CarlNote that Upnews is back up. http://www.rebol.net/cgi-bin/upnews.r4-Mar 19:44
54CarlEveryone here should note this blog: http://www.rebol.net/upnews/0022.html4-Mar 19:42
53CarlQ: "so there's no way to indicate who is working on each bug?" A: There used to be. It was removed due to non-usage.3-Mar 21:39
52CarlGabriele wrote: "the tracker here was only meant to prioritize what to fix for this release"

That is correct. Only for priorities and tracking the fix as a group.

3-Mar 21:36
51BrentSounds good. I gotta take my son to baseball practice. I'll catch up with you guys tomorrow. Cheers.3-Mar 21:31
50Henrikyep3-Mar 21:29
49BrentI'll review it in more detail. Maarten was heading that up, right?3-Mar 21:29
48HenrikBrent, I don't know if you followed the R3 alpha release process. It's listed in docbase and perhaps we can repeat it.3-Mar 21:26
47BrianHMezzanines group created, for coordinating mezzanine development.3-Mar 21:25
46PekrI would not like the group to spend more than one week non 2.7.6 and then move forward. Something like 3 weeks is big loss for R3 imo ...3-Mar 21:25
45BrentOr do I get to whip out a can if Carl starts slacking off on fixing these bugs??? ;-)3-Mar 21:25
44Henrikrelease coordination as well?3-Mar 21:25
43Brentalrighty then. so I guess I'll be more coordinating the testing once the bugs are fixed?3-Mar 21:24
42PekrI think that for now we should use just commone sense and whatever that works ...3-Mar 21:24
41Pekras for practical usability we only need Fixed for release: xy, then we could auto-generate output with simply change-log. But we will see, maybe even RAMBO does not survive, as there is planned bugbase for devbase ...3-Mar 21:24
40BrianHWe need to replicate some of the communications infrastructure from the R3 world.3-Mar 21:24
39HenrikI don't know if we'll fix bugs in the editor. There are some annoyances, but not sure they are worth going at.3-Mar 21:24
38Henrikall RAMBO bugs listed in the tracker are internal, so only Carl can fix them.3-Mar 21:23
37BrianHOnly Carl can fix native or runtime bugs. Mezzanine bugs have generally been fixed by whoever has the most experience in the area.3-Mar 21:22
36Brentah, that makes it a bit simpler, I guess.3-Mar 21:22
35Henrikno. It's assumed that Carl is working on them.3-Mar 21:22
34Brentso there's no way to indicate who is working on each bug?3-Mar 21:21
33HenrikWhen the bug is confirmed, Carl usually sets them as Reviewed. Then Built and the Fixed. I don't know if anyone else but Carl is able to fix these bugs.3-Mar 21:21
32Brentwho it's assigned to, that is3-Mar 21:20
31Brentis there an established method for assigning tracker items? there is a "submitted" field but not "assigned".3-Mar 21:19
30HenrikI would just have wanted Tracker and RAMBO to be the same thing.3-Mar 21:19
29PekrI think that for the future RAMBO should be extended. Not much is needed imo. We could add also planning, marking some bugs as to be fixed for next milestone, and work on them, etc., but we will see :-)3-Mar 21:18
28BrianHWe have to do that already.3-Mar 21:17
27Gabrielethat's ok with me, but you'll still have to search rambo to see if anyone has posted it in the meantime.3-Mar 21:16
26Henrikhow about we wait until the bugs are fixed, and then put them in RAMBO as fixed?3-Mar 21:15
25Gabrielebut... feel free to ignore me.3-Mar 21:14
24Gabrielethere are many more bugs in rambo than here. the tracker here was only meant to prioritize what to fix for this release (as opposed to what to fix in all the following releases)3-Mar 21:14
23Henrikbut it is a hassle to keep them synced3-Mar 21:13
22HenrikRambo would be for public viewing of bug fixes3-Mar 21:13
21BrianHThat kind of reduces the value of using the tracker here.3-Mar 21:12
20Gabrielehenrik: not yet, but it could. brian: i think it would be useful to users that are not in this world.3-Mar 21:12
19BrianHWe retrofitted some of the items with RAMBO entries after doing some research. Do we need to add RAMBO entries for the rest?3-Mar 21:12
18Henrikis the changelog generated from rambo fixes?3-Mar 21:11
17Gabrielei'm talking about those few :)3-Mar 21:11
16Brentall but a few have RAMBO numbers already3-Mar 21:10
15Gabrielewouldn't it be a good idea to make sure that all the bugs listed here are also listed in RAMBO?3-Mar 21:10
14BrianHIn here? Up to date but incomplete.3-Mar 21:09
13Brentso how up to date is Tracker?3-Mar 21:08
12CarlSo, in conclusion, I think Maarten may be too busy... so let's go ahead build the lists and have Brent help keep us on track.3-Mar 21:04
11CarlBrent has also stepped forward and offered his project management abilities.3-Mar 20:26
10Carl(Or that he's too busy right now.)3-Mar 20:24
9CarlOk, so do you think maybe I twisted Maarten's arm to hard to be PM on V2. I kind of got the sense that maybe it was asking too much.3-Mar 20:23
8CarlG: ok. I can move those as a file to here. And then perhaps someone can evaluate and list them here as needed.3-Mar 20:19
7CarlYes, SDK is included.3-Mar 20:18
6GabrieleCarl: please look at the V 2.7 group on rebol-hq, and the checklists there. i think a number of bugs were already fixed from 2.7.5.3-Mar 14:45
5PaulI agree that we need to have SDK otherwise many are not going to benefit from the changes if they can't use the changes in their implementation.3-Mar 13:31
4RobertIMO SDK is mandatory otherwise it doesn't make any sense.3-Mar 12:10
3AshleyI hope that includes an SDK release as well?3-Mar 3:46
2CarlV 2.7.6 Goal: March 7, 2008

Definition: Select a small number of bugs, fix them, and get it released.

2-Mar 23:01
1CarlThis world was created because we plan to continue support for R2 for quite some time into the future... And, all of the discussions related to R2 will clutter up and get confused in the R3-alpha world.2-Mar 22:56

Return to Index Page