Re: [aerogear-dev] Maintenance branches

-SNAPSHOT makes my skin crawl. Can we use the more semver way of -pre?

/me likes short version names 1.0.0 -> 1.0.1-pre hack hack hack 1.0.1 -> 1.0.2-pre hack hack hack hack hack hack hack hack hack hack hack hack 1.1.0 -> 1.1.1-pre Not going to fight to the death for it but just feels better with our new version system. On Mar 26, 2013, at 10:18 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > This is a place where we would benefit of maven-release-plugin semantics > > 1.0.0 -> 1.0.1-SNAPSHOT > hack hack hack > 1.0.1 -> 1.0.2-SNAPSHOT > hack hack hack > hack hack hack > hack hack hack > hack hack hack > 1.1.0 -> 1.1.1-SNAPSHOT > > does it make sense? the .y. component bumps when there are enough changes/features/API changes (non breaking or easy to fix) > > On 26/03/2013, at 09:40, danielbevenius <daniel.bevenius(a)gmail.com&gt; wrote: > >> Sort of related to this is what version we should have in the master branch. >> >> For example, we are about to release aerogear-controller 1.0.0. Should the >> version of master be updated to 1.1.0-SNAPSHOT or somethings else? >> >> >> >> -- >> View this message in context: http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-Maintenance-branch... >> Sent from the aerogear-dev mailing list archive at Nabble.com. >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > -- > qmx > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev