CalVer is a versioning convention based on your project's release calendar, instead of arbitrary numbers.

See the diff of two crate versions directly in the browser. All is happening in the browser 😳

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 useful utility 👍

1. When you need to release a breaking change—any breaking change—you do it in a major version. Period. No excuses.
2. You need to find a different way to communicate more significant project-wide changes and improvements. Major version numbers can’t do double duty as both breaking-change indicator and marketing hook.

About the second point, I would argue that giving an name is greater :D
Ubuntu uses it... Hahaha I read it as I write it.

Why are lockfiles critical for supply chain ?

You are protected from a silent update of the package at the same version.

The articles provide a table with the different related commands 👍‍

The reality is, is that semver doesn't communicate what has changed or how much has changed, but rather how the changes affect the user. I think the biggest problem with semver, is maintainers pretending to follow semver. Changing the names would go a long way to clearly communicating the intention and meaning behind each number.

👍

This way we know all how to give a proper version to a software 😄
Clear, efficient and provided with tools (parser, regex, etc...) 👍