Jukka Zitting wrote: > Hi, > > On Tue, May 12, 2009 at 5:56 PM, Thilo Goetz <[email protected]> wrote: >> * Getting releases approved by the incubator PMC is >> intensely painful. > > I should be able to help with that.
That would be great :-) > >> * The version number: we could go with 2.3, or 2.2.3. >> Arguments could be found for each, I don't have a strong >> opinion. > > The number of improvements and new features tagged in Jira for the > next release suggest that it should be called 2.3, though I'm not too > familiar with your version numbering strategy. Yes, I tend towards 2.3 as well, particularly if we change the packaging around. > >> Time frame (straw man proposal): >> >> 6/15 end of coding, only bug fixes after this point >> 6/22 end of testing, create distribution and submit for >> release vote >> 6/30 release > > An alternative would be to create a release branch on 6/15 and > selectively merge only bug fixes from trunk after that. This approach > has the benefit that it allows normal development to continue in trunk > while the release is being prepared. Not sure if it's worth the extra > trouble though. We're usually all busy getting the release out at a time like that, so nobody is missing a dev stream. If anybody is, we can always branch. > > BR, > > Jukka Zitting
