On 14 January 2011 14:25, Geoffrey De Smet <span dir="ltr"><<a href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"><div class="im">
<blockquote type="cite">But Drools isn't being developed according
to some standard Development Life Cycle.</blockquote></div>
Not true, but the development process should be documented more. See
/README.txt<br></div></blockquote><div><br>Well... Basically, we agree ;-)<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div text="#000000" bgcolor="#ffffff">
We have plenty of things already set-up. Most recently we defined
they idea focusing on "branch day" instead of "release day".<br>
Feel free to open discussions on any other improvements we should
do: you're right there's much to do. But 1 at a time please, so
people can adjust to them.<br></div></blockquote><div><br>A recent exchange with Edson/IRC has brought up a "howto" for the full branch - change - push cycle. I'm collecting...<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">
<br>
Next thing is the split-up of the build and repositories (if
possible).<br></div></blockquote><div><br>Ah, a consummation. Devoutly to be wish'd!<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff">
After that we'll look into a lieutenant git model per repository,
which is basically the coordination CM role you speak of :)<br></div></blockquote><div><br>Great.<br>-W<br><br></div></div><br>