[rules-dev] [Proposal] Less horrible releases: 1) Don't add new features after CR1 is branched

[Geoffrey De Smet]

Hi guys,

This release (5.2.0) has been pretty horrible.
We 've lost lots of time on:
- cherry-picking commits
- testing everything again and again (and again) /because the last 
cherry-picked commit just changed everything again/
Which results in months of delay (branch date was 28-APR and release 
date was 23-JUN).

Let's make the next release less horrible :)
I believe this organization problem is very easy to fix, by introducing 
this rule:
*Don't add new features after CR1 is branched* (on the CR/final release 
branch)

What do you think? Do you think this is a good idea?

-- 
With kind regards,
Geoffrey De Smet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/rules-dev/attachments/20110624/5ea9cdee/attachment.html