On Tue, Mar 26, 2013 at 4:18 PM, Douglas Campos <qmx@qmx.me> 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?

Yo - it does;

the 'master' would be the -SNAPSHOT one...

now... imagine the master is at 1.0.3-SNAPSHOT and we need a patch for the 1.0.1....

a '1.0.1.x' branch would be - at that point when it's needed - created out of 1.0.1 TAG

right ?

<3 maven release plugin <3

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@gmail.com> 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-branches-tp2031p2080.html
> Sent from the aerogear-dev mailing list archive at Nabble.com.
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev

--
qmx

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev