Hi,
On 5/6/16 10:08 PM, Christian Schulte wrote:
This would need to be enforced automatically in a way that a release
with a version string not containing three digits cannot be performed.
This could be handled via writing a Maven Enforcer Plugin rule...
Maybe also get rid of -alpha, -beta, -whatever that way.
We have only a single shared component in that kind of state...may be
this can be retired (if it is not used anywhere)...
So that shouldn't a big problem to do.....
Am 05/06/16 um 22:00 schrieb Karl Heinz Marbaise:
Hi to all,
I would like to suggest to keep the version number of the plugins and
shared components to the following format (and may be also things we are
using like plexus?):
Major.Minor.Patch(-SNAPSHOT):
(Following SemVer.org):
So adding a new functionality which will not break the 3.0.X parts...so
you can upgrade without breaking...for example:
3.0.23
now adding a new functionality which does not influence the older one
should be:
3.1.0
So we should prevent changing it to:
3.1
So introducing a break in API must change the Major version and would
look like this:
4.0.0 and 4.0
So consistently using a three number form Major.Minor.Patch ..
Othwerise it's not a clear line from the user perspective...At the
moment we have the chance to make things better than in the past...
WDYT ?
Kind regards
Karl Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
