<br><br><div class="gmail_quote">On Tue, Mar 26, 2013 at 4:18 PM, Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is a place where we would benefit of maven-release-plugin semantics<br>
<br>
1.0.0 -> 1.0.1-SNAPSHOT<br>
hack hack hack<br>
1.0.1 -> 1.0.2-SNAPSHOT<br>
hack hack hack<br>
hack hack hack<br>
hack hack hack<br>
hack hack hack<br>
1.1.0 -> 1.1.1-SNAPSHOT<br>
<br>
does it make sense?</blockquote><div><br></div><div><br></div><div>Yo - it does;</div><div>the 'master' would be the -SNAPSHOT one...</div><div><br></div><div>now... imagine the master is at 1.0.3-SNAPSHOT and we need a patch for the 1.0.1....</div>
<div>a '1.0.1.x' branch would be - at that point when it's needed - created out of 1.0.1 TAG </div><div><br></div><div>right ?</div><div><br></div><div><3 maven release plugin <3</div><div><br></div><div>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> the .y. component bumps when there are enough changes/features/API changes (non breaking or easy to fix)<br>
<div class="HOEnZb"><div class="h5"><br>
On 26/03/2013, at 09:40, danielbevenius <<a href="mailto:daniel.bevenius@gmail.com">daniel.bevenius@gmail.com</a>> wrote:<br>
<br>
> Sort of related to this is what version we should have in the master branch.<br>
><br>
> For example, we are about to release aerogear-controller 1.0.0. Should the<br>
> version of master be updated to 1.1.0-SNAPSHOT or somethings else?<br>
><br>
><br>
><br>
> --<br>
> View this message in context: <a href="http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Maintenance-branches-tp2031p2080.html" target="_blank">http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Maintenance-branches-tp2031p2080.html</a><br>
> Sent from the aerogear-dev mailing list archive at Nabble.com.<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>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
qmx<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<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>
</div></div></blockquote></div><br><br clear="all"><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>