+1 to no new features after CR1.<br><br><div class="gmail_quote">On 24 June 2011 10:19, Jervis Liu <span dir="ltr"><<a href="mailto:jliu@redhat.com">jliu@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<u></u>
<div bgcolor="#ffffff" text="#000000"><div class="im">
On 2011/6/24 12:49, Geoffrey De Smet wrote:
<blockquote type="cite">
Hi guys,<br>
<br>
This release (5.2.0) has been pretty horrible.<br>
We 've lost lots of time on:<br>
- cherry-picking commits<br>
- testing everything again and again (and again) <i>because the
last cherry-picked commit just changed everything again</i><br>
Which results in months of delay (branch date was 28-APR and
release date was 23-JUN).<br>
<br>
Let's make the next release less horrible :)<br>
I believe this organization problem is very easy to fix, by
introducing this rule:<br>
<b>Don't add new features after CR1 is branched</b> (on the
CR/final release branch)<br>
<br>
</blockquote></div>
+1<br>
<br>
Jervis<br>
<blockquote type="cite"><div class="im">
What do you think? Do you think this is a good idea?<br>
<pre cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</div><pre><fieldset></fieldset>
_______________________________________________
rules-dev mailing list
<div class="im"><a href="mailto:rules-dev@lists.jboss.org" target="_blank">rules-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</div></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
rules-dev mailing list<br>
<a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/rules-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
<br></blockquote></div><br>