<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Not that I am mad, but yea, git knows which parent revision it came
from and even which commits were cherry picked from master etc.<br>
Sticking the revision in there isn't really useful, as it's not
really the revision that is going to be released:<br>
there will be bugfix commits applied and possibly even big merges
from master.<br>
<br>
What is bad, is the confusion this creates for anyone who isn't
working on the release.<br>
What is the release branch for M1? Is it <i>5.2.0.M1.x</i> or <i>5.2.0-M1.901ad86</i>?<br>
<i>There can only be one.</i> And the rest of us need to be able to
guess it.<br>
<br>
So follow the naming convention we discussed earlier:<br>
<ul>
<li>all release branches should end in ".x"</li>
<ul>
<li>To avoid confusing them with release tags or topic branches<br>
</li>
</ul>
<li>all release tags should be equal to the version the represent</li>
<ul>
<li>and a tag should only be set just before it's uploaded to
the maven repo and then NEVER changed</li>
<ul>
<li>Yes, with never I mean even if the release is broken. Then
just do a hotfix .1 (for example 5.1.1 or 5.2.0.M1.1)
version</li>
<ul>
<li>because maven repo's are cached locally forever.</li>
</ul>
</ul>
</ul>
</ul>
for example:<br>
<ul>
<li>release branch 5.1.x</li>
<ul>
<li>with release tags 5.1.0.CR1, 5.1.0.FINAL, 5.1.1.FINAL<br>
</li>
</ul>
<li>release branch 5.2.0.M1.x</li>
<ul>
<li>with release tags 5.2.0.M1<br>
</li>
</ul>
<li>release branch 5.2.0.M2.x</li>
<ul>
<li>with release tags 5.2.0.M2</li>
</ul>
<li>release branch 5.2.x</li>
<ul>
<li>with release tags 5.2.0.CR1, 5.2.0.FINAL, 5.2.1.FINAL</li>
</ul>
</ul>
Depending on the JBoss version number conventions, the finals
release versions should end in FINAL or GA or nothing.<br>
It looks like it's ".FINAL" these days, not sure.<br>
WDYT?<br>
<br>
Op 23-12-10 09:41, Michael Anstis schreef:
<blockquote
cite="mid:AANLkTik92+Sc2fqqAu_Bped065Eke-dzv1jjM-2f-JU4@mail.gmail.com"
type="cite">Ge0ffrey won't be happy ;)<br>
<br>
I'm sure he was keen to drop the revision\version number from the
branch name; hence 5.2.0-M1 would probably have sufficed :)<br>
<br>
Cheers,<br>
<br>
Mike<br>
<br>
<div class="gmail_quote">
On 23 December 2010 06:22, Jervis Liu <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:jliu@redhat.com">jliu@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Hi, I've created a new branch for Drools 5.2.0-M1 release:<br>
5.2.0-M1.901ad86. This branch is created from version<br>
901ad86c8fad67051646. Check<br>
<a moz-do-not-send="true"
href="https://github.com/droolsjbpm/droolsjbpm/commits/master?page=1"
target="_blank">https://github.com/droolsjbpm/droolsjbpm/commits/master?page=1</a>
for<br>
version details. Please let me know if you think this branch
should not<br>
contain a certain commit or a certain commit for 5.2.0-M1
release is<br>
missed on this branch.<br>
<br>
Cheers,<br>
Jervis<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>
</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>