All,
I think we owe it to the users that take the time to report bugs to do a
bug release. Remember that the release needs to come from the fixes branch
that Rick started:
https://oorexx.svn.sourceforge.net/svnroot/oorexx/main/branches/4.1/
For doc fixes, we need the same general mechanism that Rick proposed, so I
have branched the 4.1.0 doc release to:
https://oorexx.svn.sourceforge.net/svnroot/oorexx/docs/branches/4.1/
I started at the top of the bug list in the pending state checking to be
sure that a fix that needed to be in both main and the fixes branch was
indeed in the fixes branch, and adding a comment as appropriate.
Jean-Louis and Rick had already been commenting that the fix was applied to
both trees.
Some of the fixes in the pending state, will not actually go into a bug
fix, and in my opinion, those should just be closed at this time.
For instance, a bug for the 4.2.0 ooDialog would not be included in a 4.1.0
bug fix, the bug did not exist there. Likewise it wouldn't be listed in a
future release because the bug never existed in a released version of
ooDialog. There may, or may not, be some similar bugs in the pending state.
I don't have any particular time frame in mind, I just wanted to get the
ball rolling.
--
Mark Miesfeld
------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
