On Tue, 2004-06-08 at 09:13, robert burrell donkin wrote: > i've been pleased to see that simon's been hard at work with TODO lists > for 1.7 and 2.0 (at least, i think it's simon - whoever it is, what not > create a user profile then we'll all know).
Yep, that's me. I see that some WIKI edits come up with the name of the person doing it, but I haven't been able to figure out how to do that. I can't see any "login" or "create account" or similar options anywhere on the MoinMoin pages. Can you point me in the right direction? > > (most people will probably be aware that) i've decided to cut release > again (potential release managers may want to take a look at this > thread > http://nagoya.apache.org/eyebrowse/ReadMsg? > [EMAIL PROTECTED]&msgNo=3265) and that i've been pushing > forward new releases for logging and beanutils. > > the main motivation for these releases to enable downstream consumers > of our libraries to have a smooth upgrade path which sidesteps binary > compatibility issues with commons collections versions. > > digester is the next in my sights for a service release. That's good news. > since this is > release is primarily aimed at helping downstream consumers by resolving > dependency issues (rather than one aimed at adding functionality) it'd > probably be a good idea to move quickly to take a release branch > containing the current code base so that the work for the meatier > release (with more functionality) can proceed in parallel with the > release process (that's usually a little drawn out). Well, there have been quite a few new features added in the last 12 months, and very few bugs have surfaced to be fixed. So as the current release notes say it will be mostly a "feature" release if you use HEAD. The existing CVS HEAD code is pretty stable and well tested, so I would definitely recommend releasing from HEAD. Having the new release reduce the dependencies will be nice. The only developers who have added features to Digester for a long while have been you and I (with pushing from Remy and Emmanuel in places). And despite that TODO list, I don't intend to tackle any of those for at least a month or so. So a separate branch for concurrent development may not be necessary. > > if this seems like a good plan, i'll write it up (on the wiki) tomorrow > and move towards a vote on the plan pretty soon. as soon as we can > decide on the right number for the features release, i'll put an > outline release plan on the wiki. That's great. After an exchange of emails with Lars Kuehne I have decided to join in with his "clirr" project (http://clirr.sourceforge.net/) after all, so if I get *my* act together, we may even be able to include an API differences and binary compatibility report generated by "clirr". Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
