On Tue, Jul 10, 2012 at 9:10 AM, Rick McGuire <[email protected]> wrote: > On Tue, Jul 10, 2012 at 11:50 AM, Mark Miesfeld <[email protected]> wrote: >> Hi All, >> >> Thinking ahead to the next release ... >> >> 1.) Put the current ooDialog stuff that is ready in the 4.1 fixes >> branch. Do a bug fix + ooDialog release with a beta starting in >> August. > > Some of the stuff I've added to the trunk version is currently in a > bit of a half-baked state. It's sort of the basis for implementing > catch/finally blocks ala NetRexx, but there's a lot more work needed > to take the next step. The trunk version could be used as a basis, > but there are a few features that probably need to be buried under > the covers in order for it to go out. > > Even if you base this on the 4.1 branch, it probably should be labeled > the 4.2.0 release, with trunk then getting pushed to 4.3
I was thinking more along those lines. Push trunk to 4.3, branch the current 4.1 to 4.2. Base a 4.2.0 release on 4.2. That would leave a 4.2 branch for bug fixes. Would we still need a 4.1 branch? The 4.2 branch would essentially be the 4.1 fixes branch with just a version bump, 4.1 to 4.2. >> 2.) Do a release with ooDialog and XML as major enhancements. Start a >> beta around August if that's practical with the XML stuff. > > I don't see August as a practical date for the XML stuff being ready. > At this point, I'm not even sure if January is practical, given the > amount of work still required. > > However, I've opened quite a few small RFEs recently based on things > that have annoyed me while writing the XML support. I've just been > opening those with the intent of returning to them once I've going the > XML support a little further along. I could re-prioritize and see if > I can knock off some of these. Most of these would be simple to > implement (probably harder to write the tests and docs than the actual > code). Maybe set a deadline of September. I'd actually like to use a > few of those for the XML code, even though it means it would be tied > to 4.2.0 release. Since it already uses 4.1-specific features, I > guess that's not that big of a deal. Maybe, do a 4.2.0 release based on my #1 option in August. Then do a next release around a January time frame that would have XML and / or the small RFEs. This would fit in with my desire to do at least 2 or 3 smaller releases per year so that fixed bugs get picked up sooner. >> 3.) I can do an ooDialog only beta / release independent of the >> interpreter. ooDialog would have an installer that drops it into any >> 4.1.0 ooRexx installation. > > I'm comfortable with that too. Yeah, I am too. So, I'd like to go with #1 or #3 and plan on a next release around Jan 1 time frame to pick up Rick's new stuff. -- Mark Miesfeld ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
