Okay, I have copied ooRexx 4.2.0 main and docs branch to release in svn. I
renamed the 4.2.0 branch to 4.2 branch to be the fixes branch for 4.2.
I created the 4.2.0 release directory on SourceForge and put the Windows
builds and the misc doc files there.
David -
I have the 4.2.0 directory as "Staged". If you are logged in as Admin you
can see it, if not you don't see it. It looks like you can just click the
I (info) icon, uncheck the Staged check box, and save at any time to change
the directory from staged to not statge. Otherwise it becomes unstaged on
Tuesday.
I didn't do anything with the oorexx-docs directory on SourceForge. It
still has the 4.2.0 beta docs.
I didn't put a 4.2.0 debug build up yet. I'm doing a little research and
will probably hold off on that until I'm back in town.
Rick and Mike -
It looks like the winDbg debugger supports JIT debugging, which means it
should automatically break in if a crash happens on a system it is
installed on. It is a free download. If we supply the .pdb files with a
debug build, we should be able to get good information from a crash on a
user's system, if they will go to the trouble of installing the Windows
debugging tools along with the ooRexx debug build.
--
Mark Miesfeld
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk___
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
