Hi All & Maven Devs

 

My name is Lukas, I'm a software engineer working at some very little
company located in Switzerland (called Quatico).

I wanted to let you know that the versioning that is used in (as far as I
can see) all Maven Plugins (e.g. Apache Maven Install Plugin 3.0.0-M1) is
very confusing <to the world>.

I can see on the corresponding Website (e.g.
https://maven.apache.org/plugins/maven-install-plugin/download.cgi ) the
these milestone releases are declared to be stable.

 

My company did not upgrade plugin versions basically for some years now
because (when just seeing the version itself) decided "Nope, its only a
milestone, thus not stable".

So in contrast to the maven plugin versions, the community is pretty clear
about what x.y.z-M1 means: It's a pre-release for early testing purposes
(e.g. see you "partner" projects explanation for it here
https://en.wikipedia.org/wiki/Software_versioning ).

 

I don't want to complain (I now know the versions are stable) but the usage
of your new version would probably pike much quicker around the work if you
followed the "regular" versioning scheme.

Why use the Major part (3), then completely ignoring Minor (always 0) and
Patch (always 0 as well) parts, to then fall back to Milestones? I cannot
see an advantage in it.

 

Hope the input might help!

 

Cheers

Lukas

 

Reply via email to