[aerogear-dev] Maintenance branches
Bruno Oliveira
bruno at abstractj.org
Tue Mar 26 11:25:05 EDT 2013
SNAPSHOT because is a pattern on nexus :)
--
"The measure of a man is what he does with power" - Plato
-
@abstractj
-
Volenti Nihil Difficile
On Tuesday, March 26, 2013 at 12:23 PM, Matthias Wessendorf wrote:
>
>
> On Tue, Mar 26, 2013 at 4:21 PM, Kris Borchers <kris at redhat.com (mailto:kris at redhat.com)> wrote:
> > -SNAPSHOT makes my skin crawl. Can we use the more semver way of -pre?
>
> :-)
>
> I have no pref. if the thing is called 'snapshot', '-pre' or even '-soon' :)
>
> >
> > /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 at qmx.me (mailto:qmx at 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? 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 at gmail.com (mailto:daniel.bevenius at 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 (http://Nabble.com).
> > >> _______________________________________________
> > >> aerogear-dev mailing list
> > >> aerogear-dev at lists.jboss.org (mailto:aerogear-dev at lists.jboss.org)
> > >> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> > >
> > > --
> > > qmx
> > >
> > >
> > > _______________________________________________
> > > aerogear-dev mailing list
> > > aerogear-dev at lists.jboss.org (mailto:aerogear-dev at lists.jboss.org)
> > > https://lists.jboss.org/mailman/listinfo/aerogear-dev
> >
> >
> > _______________________________________________
> > aerogear-dev mailing list
> > aerogear-dev at lists.jboss.org (mailto:aerogear-dev at lists.jboss.org)
> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org (mailto:aerogear-dev at lists.jboss.org)
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130326/13f1e77f/attachment.html
More information about the aerogear-dev
mailing list