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

[Geoffrey De Smet]

Just to clarify (to avoid misuse of my words): the release itself is not 
horrible, it's great :)
There have been loads of testing and bugfixing on this release.

But /the release process is horrible/, so let's improve that.

-- 
With kind regards,
Geoffrey De Smet


Op 24-06-11 11:19, Jervis Liu schreef:
> On 2011/6/24 12:49, Geoffrey De Smet wrote:
>> 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)
>>
> +1
>
> Jervis
>> What do you think? Do you think this is a good idea?
>> -- 
>> With kind regards,
>> Geoffrey De Smet
>>
>>
>> _______________________________________________
>> rules-dev mailing list
>> rules-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
> _______________________________________________
> rules-dev mailing list
> rules-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-dev

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