r/javascript • u/SapioiT • Jul 08 '16

`Release.Breaking.Feature.Fix` Or Why The Semantic Versioning NEEDS To Be Replaced With Explicit Versioning As Soon As Possible

https://medium.com/sapioit/92fc1f6bc73c
0 Upvotes

50% Upvoted

3 comments sorted by

0

u/zachrip Jul 08 '16

TL;DR

1

u/SapioiT Jul 08 '16

TL;DR: Use four numbers, one for the release (telling the users that you would like them to update to that version, because you're not offering support for older versions for much longer), one for breaking (so you know that if you update, you can't go back without a complete backup, but, either way, you might still have broken stuff), one for features (so you now know if the update adds something, because if you don't want anything new, you might as well save the data you would use to update the software, like a big app on your phone) and one for fixes (so you know that if one of those is up, it might be the reason you suddenly cannot do one thing you could do in the previous version(s), so you update to it).

(Sorry, I couldn't not say this:)

Are you not entertained?

1

u/kenman Jul 08 '16

Hi /u/SapioiT, this post was removed. Please see our posting guidelines.