<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I don't believe we can ever get the release perfect, but knowing the dates right after the previous release would help with the planning.</div><div>Maybe the last 2 weeks should be done using a release branch? We have community people working on new features and using the master to get the codes stable would slow them down. 5.2.x branch was pretty long, still I didn't find it that hard to cherry pick and merge my bug fixes.</div><div><br></div><div>Toni</div><br><div><div>On Jun 24, 2011, at 1:25 PM, Geoffrey De Smet wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div text="#000000" bgcolor="#ffffff">
If we do more releases, the releases process will become easier and
maybe even a non-event.<br>
At least, I believe that paradox :)<br>
<br>
Here's what I propose:<br>
- For the next 4 weeks, until 22-JUL, we focus on big, risky
features.<br>
- The 2 weeks after that, until 5-AUG, we focus on bugfixing and <i>avoid
risky changes</i>.<br>
On 5-AUG, I release 5.3.0.Beta1 directly from master.<br>
If needed, we can call it 5.3.0.Alpha1 instead.<br>
<br>
This will allow our users to verify backwards compatibility and new
features sooner<br>
and give us feed-back sooner.<br>
<br>
What do you think? Good idea or too ambitious?<br>
<pre class="moz-signature" cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</div>
_______________________________________________<br>rules-dev mailing list<br><a href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/rules-dev<br></blockquote></div><br></body></html>