<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<blockquote type="cite">But Drools isn't being developed according
to some standard Development Life Cycle.</blockquote>
Not true, but the development process should be documented more. See
/README.txt<br>
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>
<br>
Next thing is the split-up of the build and repositories (if
possible).<br>
After that we'll look into a lieutenant git model per repository,
which is basically the coordination CM role you speak of :)<br>
<br>
Op 03-01-11 14:49, Wolfgang Laun schreef:
<blockquote
cite="mid:AANLkTinuVE7Nmj+FJJh9oe1wp9mi38qa=Ubxhic2O-7U@mail.gmail.com"
type="cite">OK, locally I can do whatever. But how am I supposed
to get my work up to remote and master? Merge locally and then
push?<br>
<br>
10+ years with CM in my organisation have shown us that branched
work is best integrated into the main (master) branch by some
coordinating CM role. But Drools isn't being developed according
to some standard Development Life Cycle.<br>
<br>
-W<br>
<br>
<br>
<div class="gmail_quote">On 3 January 2011 14:38, ge0ffrey <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:ge0ffrey.spam@gmail.com">ge0ffrey.spam@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid
rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left:
1ex;">
<br>
Imo, topic branches should be local<br>
or remote on a fork.<br>
i dont think we should litter reference with remote topic
branches.<br>
it should only have release branches.<br>
look at hibernate on github.<br>
<font color="#888888">--<br>
View this message in context: <a moz-do-not-send="true"
href="http://drools-java-rules-engine.46999.n3.nabble.com/git-branches-origin-username-tp2180410p2184778.html"
target="_blank">http://drools-java-rules-engine.46999.n3.nabble.com/git-branches-origin-username-tp2180410p2184778.html</a><br>
Sent from the Drools - Dev mailing list archive at
Nabble.com.<br>
_______________________________________________<br>
rules-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/rules-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/rules-dev</a><br>
</font></blockquote>
</div>
<br>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
rules-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:rules-dev@lists.jboss.org">rules-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/rules-dev">https://lists.jboss.org/mailman/listinfo/rules-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</body>
</html>