On Thu, Mar 5, 2009 at 1:19 AM, ant elder <[email protected]> wrote: > > > On Mon, Mar 2, 2009 at 11:18 AM, ant elder <[email protected]> wrote: >> >> We've talk about a 6 week release cycle on 2.x and the M1 RC1 was done on >> Feb 9 so six weeks from then is in 3 weeks on March 23rd. That seems like a >> fine date to aim for M2 RC1 to me, does it sounds ok for everyone? >> >> One of the main things I'd like to get done for M2 is to update the build >> to use the Maven release plugin (TUSCANY-2813) as has been done for the >> Tuscany plugin builds, that s going to change the release process quite a >> bit so I'm happy to be the M2 RM to make sure its working properly but if >> anyone else who hasn't done it before would like a go that would be great >> too so just volunteer and i can help out with any problems there may be with >> getting the new release process running smoothly. >> >> ...ant >> > > No comments so I'll assume this is ok and plan to take an M2 branch around > the 19th of March (thats 2 weeks from now) and an RC out by the 23rd. >
We successfully did 2.0 M1 without a branch, while this has the side effect of caution during the release candidate process, it helps by avoiding inconsistency when people forget to merge, and avoid merging in general. > ...ant > > > -- Luciano Resende Apache Tuscany, Apache PhotArk http://people.apache.org/~lresende http://lresende.blogspot.com/
