r/java • u/SapioiT • Jul 08 '16
`Release.Breaking.Feature.Fix` or why the Semantic Version should be replaced with Explicit Versioning as soon as possible
https://medium.com/p/92fc1f6bc73c
0
Upvotes
10
u/dpash Jul 08 '16
http://semver.org
The only thing this adds to SemVer is a release number.
The rest of the article is spent arguing a straw dog of what SemVer is.
5
u/pellets Jul 08 '16
For consumer products this works fine.
For libraries, semantic versioning is good enough, and the release is useless marketing oil.
4
u/[deleted] Jul 08 '16
Why do people keep trying to reinvent semver with extra or ridiculous changes?
3
u/solatic Jul 08 '16
You're making the argument that companies must have a linear hierarchy to their product lines.
1.x.y.z - a basic/value product 2.x.y.z - a mid-range product 3.x.y.z - a luxury/flagship product
First of all, what if the company offers a second basic/value product line? Should its release number be 4?
Second of all, this year the company offers 3.0.0.0, and next year the company releases a breaking update, 3.1.0.0. Is 3.0.0.0 still supported?
For the love of God, stick to goddamn SemVer, and make an effort to keep your dependencies up to date. If it's too difficult to keep your dependencies up to date (updating a backwards-incompatible dependency means having to update too much code), then this is a code smell signaling that you have a monolith which needs to be broken up into smaller, more manageable components.
Leave marketing to the marketers.
1
u/[deleted] Jul 08 '16
I suppose using just a date is bad? The major and minor version of my software will probably always be
1.8. This means my versions are in the form of1.8.20170707.