Diagram with large number (following semantic versioning): 2.7.123
First “2” is commented: Proud version. Bump when you are proud of the release
Second “7” is commented: Default version. Just normal/okay releases
Third “123” is commented: Shame version. Bump when fixing things too embarrassing to admit

Working with SemVer leads to two observations:

• only two version numbers are sufficient: there's no real difference between patch and minor.
• deprecate than remove cycle: using a major version only leads to the removal of deprecation warnings and their associated feature. It means bumping for 1 to 2 should works, if the version 1 does not throws warnings anymore.

how to judge the semver approach? Either describe the thing actually behaves (descriptivist) or describe about the right and wrong ways to use a particular tool (prescriptivist).

Another instance of this pattern playing out I’ve noticed are log levels. You can get very philosophical about the difference between error, warn and info. But what helps is looking at what they do:

• error pages the operator immediately.
• warn pages if it repeats frequently.
• info is what you see in the prog logs when you actively look at them.
• And debug is what your developers see when they enable extra logging.

I don't have this problem, iterating over patches, minor majors versions. When it follows SemVer then everything is good.

Réduire ses ambitions quitte à planifier les versions 3 et 4 par la même occasion est un moyen de faire baisser la pression de ses propres attentes. Ce n’est plus l’évènement mais un évènement parmi les suivants qui vient s’intégrer dans une dynamique plus globale.

A tool similar to release-it