On Mon, Jan 20, 2014 at 12:17 PM, Karel Piwko <kpiwko(a)redhat.com> wrote:
> +1 on postponing to a later point. If ready by April, should be
fine as
> well (my opinion). Bruno had a good point, that the postponed release
> should not stop us from releasing (unstable) snapshots for testing
reasons.
> I like that: Release often, release early.
What is actually an (unstable) snapshot? Could you shed more light on that?
I'd say a regular snapshot, from master branch, released to the snapshot
repo
Namely, is the "snapshot" a set of micro/minor releases of Aerogear
projects?
Or do you plan to release every Aerogear project as -SNAPSHOT? Or
introducing
-milestone/.Mx/alpha/beta/cr/timestamp/any-qualifier-you-like into version
strings?
I don't think 2/ option is a good idea, especially if SNAPSHOTs are
released
early & often. That would be a maintenance/testing nightmare, if various
SNAPSHOTs of the same project cannot be distinguished from each other and
used
within other projects.
Karel
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)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