<div class="gmail_quote">On Wed, Mar 17, 2010 at 6:03 AM, Andersen Max <span dir="ltr"><<a href="mailto:max.andersen@jboss.com">max.andersen@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
> Q: Will it be "simultaneous release" once a year like eclipse does?<br>
><br>
> No, firstly a simultaneous release implies that each module does it's major feature updates at the same time, I don't see we need to stick to that. Instead we will bundle a set of compatible modules. Secondly, we aim to release more than once a year :-)<br>
<br>
</div>What is the difference between "simultaneous release" and "bundle a set of compatible modules" ?<br></blockquote><div><br></div><div>I think what Pete is implying is that the modules don't have to be releasing at that time (or should not hold out the released until that date). Instead, we take what is stable at the time (pushing a release if absolutely necessary to integrate well) and then cut the bundle. But, to be honest, we're still in the process of establishing a strategy ;)</div>
<div><br></div><div>-Dan</div><div><br></div></div>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br>
<a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://www.google.com/profiles/dan.j.allen">http://www.google.com/profiles/dan.j.allen</a><br>