<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/29/2014 08:45 AM, Matthias
Wessendorf wrote:<br>
</div>
<blockquote
cite="mid:CAAg5f2Tsry7SKV=TzbhokwEd=Fpp6abin83-+beiKxaEV5+V8Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Hi,</div>
<div><br>
</div>
<div>now that we have released the 1.0.0.Final, there are two
'important' branches:</div>
<div><br>
</div>
<div>* master (current version is 1.1.0-SNAPSHOT)</div>
<div>* 1.0.x (current version is 1.0.1-SNAPSHOT)</div>
<div><br>
</div>
<div><br>
</div>
<div>This email is to clarify what goes in where, or tries to
:-)</div>
<div><br>
</div>
<div>I think it's quite simple. Every fix that goes into the
"1.0.x branch" needs to go into the "master branch" as well.</div>
<div><br>
</div>
<div>Once a PR has been merged to 1.0.x branch, it's the
responsibility of the PR filer to rebase against (latest)
master as well, to make sure the merge to master works without
any trouble!</div>
<div><br>
</div>
<div>While 1.0.x is really meant for bug fixes and improvements
only, the new development is going on in master (for
1.1.0-SNAPSHOT, and later) and therefore fixes that are
scheduled for 1.1.x only, should not go into the the 1.0.x
branch.</div>
<div><br>
</div>
<div>The scheudling is done via JIRA and almost all
commits/merges should have JIRA tickets attached.</div>
<div><br>
</div>
<div>Currently here are the 1.0.x related tickets:</div>
<div><a moz-do-not-send="true"
href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12325080/">https://issues.jboss.org/browse/AGPUSH/fixforversion/12325080/</a></div>
<div><a moz-do-not-send="true"
href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12325448">https://issues.jboss.org/browse/AGPUSH/fixforversion/12325448</a></div>
<div><br>
</div>
<div>As you can see, they all have the 1.1.x version label as
well. This is important and ensures (critical) bug fixes to
1.0.x are also arriving on the master branch!</div>
<div><br>
</div>
<div>The JIRAs that are scheduled for 1.1.0 are listed here:</div>
<div><a moz-do-not-send="true"
href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12323762/">https://issues.jboss.org/browse/AGPUSH/fixforversion/12323762/</a></div>
<div><br>
</div>
<div>Of course, due to the backport requirement, some of these
tickets contain 1.0.x labels on their Fix-Versions as well -
but some are exclusively scheduled for 1.1.0, and therefore
only go to master branch.</div>
<div><br>
</div>
<div>Any thoughts ? <br>
</div>
</div>
</blockquote>
+1<br>
<blockquote
cite="mid:CAAg5f2Tsry7SKV=TzbhokwEd=Fpp6abin83-+beiKxaEV5+V8Q@mail.gmail.com"
type="cite">
<div dir="ltr">
<div><br>
</div>
<div>-Matthias</div>
<div><br>
</div>
-- <br>
Matthias Wessendorf <br>
<br>
blog: <a moz-do-not-send="true"
href="http://matthiaswessendorf.wordpress.com/"
target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a moz-do-not-send="true"
href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a moz-do-not-send="true"
href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aerogear-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Summers Pittman
>>Phone:404 941 4698
>>Java is my crack.
</pre>
</body>
</html>