On Wed, 2004-06-09 at 08:50, robert burrell donkin wrote: > i think that a digester 1.6.0 service release allowing digester to be > used with either commons collections 2.x or commons-collections 3.x > would be a very good idea. this release will focus on providing a > stable, compatible dependency rather than fixing bugs or adding new > features. a subsequent release (probably 1.7.0) following soon > afterwards will focus on new material and will take a little longer to > prepare. i'm willing to act as release manager for the 1.6.0 release. > > i've created a release plan on the wiki > (http://wiki.apache.org/jakarta-commons/ > Digester_2f1_2e6_2e0ReleasePlan). please take a little time to read it > now and add any comments at the bottom or post a reply to this list.
I'm definitely in favour of a 1.6.0 release. However I'm confused about which code you intend to release. When you say you are making a "release branch", do you mean that you will tag all the HEAD code as at the current date, and later release that, after an RC cycle? Or do you mean you will be making a branch based on the 1_5_0 release, then backporting selected fixes? I would definitely recommend the first option (release from HEAD or near it). As I said in an earlier email, I have used the HEAD code extensively and have good confidence in its stability. But if this approach is taken, then it is *not* right to describe this release as a service/bugfix release, as it will have about 3 very minor bugfixes and several major new features since 1.5.0. The release notes currently in CVS (prepared by me about 4 weeks ago in preparation for a 1.6 release) describe this release as a "feature" release, and if you are intending to release code based anywhere near HEAD then I think this is the correct description. And if the HEAD code is used in the next release, then I can't see a reason for a 1.7 release within at least 6 months. Yes there is a big TO-DO suggestion list, but none of it is urgent. I just created that wiki page because over the last few months I have been writing down ideas as they occurred to me and wanted them to be available for everyone to see and comment on. I've got two other open-source projects I am working on at the moment that mean it will be a while before I am likely to get back to working on these myself.. Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
