Hi,<div>I vote for that. More release more often => Less function per release => less risk</div><div>Regards</div><div>Nicolas<br><br><div class="gmail_quote">2011/6/24 Geoffrey De Smet <span dir="ltr"><<a href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><u></u>
<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 cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</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></div>