I mean, a few numbers can't convey everything that's relevant for releases. But I like how comver explains well some of the concepts. I expand with a few more:

I mean, a few numbers can't convey everything that's relevant for releases. But I like how comver explains well some of the concepts. I expand with a few more: - Is the release stable? Alpha, beta, experimental new features? - Does the release have known vulnerabilities? How insecure is it? (of course, this changes as time passes and might stop being tracked, so it's not easy to manage) - Did a new release break back-compatibility? How much? Are we breaking everything, or just slightly changing the behavior of one function? - Does the release include new important features or API changes? - How often should I check for new releases, or how can I get notified if there are important unexpected changes? To me, any non-toy software project needs to respond very clearly to all these questions. If it does, I don't care about semver or not semver. If it doesn't, I don't care about semver or not semver.