<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#ffffff">
As promised, some more information about our move to git.<br>
Note that these changes are not in effect yet, which should happen
next Saturday.<br>
<br>
First phase (this year)<br>
==============<br>
<br>
In this phase, <b>we will keep everything as similar to SVN as
possible</b>.<br>
So the learning curve is as gentle as possible.<br>
This means:<br>
<ul>
<li><b>Same centralized model</b><br>
</li>
<ul>
<li>1 SVN repository:</li>
<ul>
<li><a class="moz-txt-link-freetext" href="https://svn.jboss.org/repos/labs/labs/jbossrules">https://svn.jboss.org/repos/labs/labs/jbossrules</a></li>
<li>1 additional anonymous repository mirror:</li>
<ul>
<li><a class="moz-txt-link-freetext" href="http://anonsvn.jboss.org/repos/labs/labs/jbossrules">http://anonsvn.jboss.org/repos/labs/labs/jbossrules</a><br>
</li>
</ul>
</ul>
<li>1 Git <i>reference</i> repository (= <i>blessed repository</i>):<br>
</li>
<ul>
<li><a class="moz-txt-link-freetext" href="https://github.com/droolsjbpm/droolsjbpm.git">https://github.com/droolsjbpm/droolsjbpm.git</a><br>
</li>
<li>No need for a separate anonymous repository <br>
</li>
</ul>
</ul>
<li><b>Same authorization</b><br>
</li>
<ul>
<li>Everyone who had write access on the SVN repository, gets
write access on the Git reference repository (for now).</li>
<ul>
<li>If they send me their login details! [1]<br>
</li>
</ul>
</ul>
<li><b>Same branches, same tags, same trunk (=master)<br>
</b></li>
<ul>
<li>master == trunk. master is just another word for trunk<i>.
trunk</i> shall hence forth be known as <i>master</i>.<br>
</li>
<li>Previous authors will be migrated correctly too, if and only
if everyone sends me his user details [1].<br>
</li>
</ul>
<li><b>Same directory structure</b> (for now)<br>
</li>
<ul>
<li>If you "git checkout master", you will see exactly the same
directories and files as you see now if you "svn checkout
trunk"</li>
<li>Our project will still build exactly the same way, don't
worry.</li>
</ul>
</ul>
I 'll also write a mail "Git migration: What do I need to do now
that it's done?" so you're up and running fast next Monday.<br>
Note that you should have already done [1] by tomorrow or you're a
lot of time waiting for authorization next Monday!<br>
Once everyone is acquainted with git, I 'll write a blog about how
outsiders can supply us pull requests instead of clumsy patches.<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="http://drools-java-rules-engine.46999.n3.nabble.com/Git-Next-Saterday-18-DEC-2010-we-are-moving-to-git-gt-Tell-me-your-github-login-before-Thursday-16-D0-td2069261.html">http://drools-java-rules-engine.46999.n3.nabble.com/Git-Next-Saterday-18-DEC-2010-we-are-moving-to-git-gt-Tell-me-your-github-login-before-Thursday-16-D0-td2069261.html</a><br>
<br>
Future phases (next year)<br>
================<br>
<br>
In future phases (probably starting around the end of January) we
might look into some bigger changes.<br>
<br>
This is also the reason why it's called <i>droolsjbpm.git</i> and
not <i>drools.git</i>.<br>
The droolsjbpm.git will be split up into git submodules called
drools.git, jbpm.git, guvnor.git, ...<br>
So you can checkout guvnor without checking out
drools-core/compiler.<br>
But droolsjbpm.git will still exist as an aggregation, so you will
also still be able to checkout everything, like you do now.<br>
All those git submodules and the aggregation repository, will all be
under the github organization jbpmdrools:<br>
<a class="moz-txt-link-freetext" href="https://github.com/droolsjbpm">https://github.com/droolsjbpm</a><br>
<pre class="moz-signature" cols="72">--
With kind regards,
Geoffrey De Smet</pre>
</body>
</html>