<div dir="ltr">sounds good</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 29 August 2014 15:28, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">good summary!<br><div><div><div class="h5"><div>On Aug 29, 2014, at 8:45 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div>
<br></div></div><blockquote type="cite"><div><div class="h5"><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 href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12325080/" target="_blank">https://issues.jboss.org/browse/AGPUSH/fixforversion/12325080/</a></div>
<div><a href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12325448" target="_blank">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 href="https://issues.jboss.org/browse/AGPUSH/fixforversion/12323762/" target="_blank">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 ? </div><div><br></div><div>-Matthias</div><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div></div>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br></div>