I feel exactly the same. A 5.0.19 release including just the fix for TAP5-714 seems reasonable.
What about issues fixed in trunk? Some of those could be merged into the 5.1 branch, thus increasing the usefulness of the release (e.g. TAP5-779 and TAP5-711 and some documentation fixes).
Cheers, Uli Am 18.11.2009 12:27 schrieb Andreas Andreou:
So, it looks like some important bugs where (or will be) fixed so, there's no reason not to do a release... For the 5.1 branch, this can happen after TAP5-714 is dealt with. I've also noticed that Robertd Zeigler has ported that asset-related fix to the 5.0 branch, but i don't think i've seen users requesting a release for that. Having said that, it seems correct and professional to also have that release, what do you think? I'll go through the 5.1 and 5.0 poms to make them use nexus - it's a good chance to test-drive the new release procedure.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
