11:40 a.m.
Hi *, inline...
On 02/24/2015 05:41 PM, John Mazzitelli wrote:
Right now I've seen version strings as 1.0-SNAPSHOT,
1.0.0-SNAPSHOT
and 1.0.0.Alpha1-SNAPSHOT.
We need to come to a consensus and be consistent. From what I
understand, people prefer:
1.0.0-SNAPSHOT
I would like to go through all our components and change their
versions to be that. It would be nice to have our first distro
release at least be consistent in naming of versions.
Some theory in favor of adding a qualifier such as Alpha[n], Beta[n],
CR[n] and Final : https://developer.jboss.org/wiki/JBossProjectVersioning
In addition, its getting annoying with having to rely on release
versions of parent pom. I'm again waiting on release 8 because I
added a new maven plugin to the parent.
Please do not commit your own changes to the parent.
https://github.com/hawkular/hawkular-parent-pom#how-to-contribute
We should move every pom over
to use 8-SNAPSHOT so we can keep picking up changes. We are moving
fast, and its slowing us down (well, me down for one) because we now
have poms that need parent pom v6 and v7 and my stuff is waiting on
8. We can release when we get some kind of product out.
Do not do that. Introducing SNAPSHOT dependencies makes builds
irreproducible and unreliable. You never know which revision you get
from the SNAPSHOTs repo. Looking at today's #hawkular logs, at least
mazz, mtho11 and stefan_n know what I am speaking about.
There is also discussion that lucas k brought up - why not have
version string for parent pom follow the same convention as
everything else (that is, why not make 8-SNAPSHOT to be
1.0.0-SNAPSHOT instead?)
It would be quite hard to find the criteria for deciding when to
increase major, minor or micro in parent.
As far as the parent contained just maven plugins, there was no
backwards compatibility in game. I admit it is quite different now that
we manage dependencies there. But I see no way how semantic versioning
could work with the parent either.
-- Peter
I'll let others decide that later. I agree
we should at least be consistent in version format for everything.
_______________________________________________ hawkular-dev mailing
list hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev