|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I did read the whole thing, and I have been working with Maven and semantic versioning for years. If you look at previous releases of this plugin, then they followed semantic versioning properly until the first release from David Tanner. I don't know why he changed it, but he didn't even change it during a major upgrade. Can you not see how this is poor engineering.
Also, please point out some evidence that semantic versioning a release as x.y-z is an acceptable practice. I agree that you can have dashes, but that is only for descriptors that are not in above-beta releases. The standard is x.y.z or major.minor.patch. In fact, this was the standard for the plugin in question.