Thanks Aidan, yes 6 weeks for hacking and testing seems reasonable. Doing a release in parallel is fine. But I assume certain fixes in trunk may need to be done in the branch and most certainly most of the fixes done on the branch may end up in the trunk. So we may need to have a good strategy in cordinating all these issues.
Rajith On Jan 11, 2008 10:15 AM, Aidan Skinner <[EMAIL PROTECTED]> wrote: > On Jan 11, 2008 2:46 PM, Rajith Attapattu <[EMAIL PROTECTED]> wrote: > > > Just to clarify, looking at the dates given for M2.1, it looks like we > are > > releasing early April. > > I thought we agreed to finish M2.1 soon and plan M3 for March time > frame? Or > > did I misunderstand the dates? > > Nope, that's the plan. It gives us 6 weeks to hack and 6 weeks to > test, which doesn't seem unreasonable given prior experience. M3 work > can happen in parallel, as it has traditonally done, as I get the > merge under way on a seperate branch (taken from trunk and tracking > changes there and pulling stuff in from M2x). > > - Aidan > -- > aim/y!:aidans42 g:[EMAIL PROTECTED] > http://aidan.skinner.me.uk/ > "It is no weakness for the wisest man to learn when he is wrong." - > Sophocles > -- Regards, Rajith Attapattu Red Hat blog: http://rajith.2rlabs.com/
