> The simple explanation is that Semantic Versioning is not at all the only way to do versioning, it is just one standard amongst others.[...]it can be confusin

> The simple explanation is that Semantic Versioning is not at all the only way to do versioning, it is just one standard amongst others.[...]it can be confusing if you think that semver is the only game in town I certainly don't think semver is the only game in town but the vast majority of versioning techniques out there are very, very similar to semver where major updates are the only ones that can affect the API. I wouldn't expect semver to suit everyone (honestly I prefer a slightly different version that was more common in the .Net universe) but at the same time most versioning techniques behave similarly. The Gtk way is fine if it works for them but it certainly isn't common. Versioning is one of the very few things that I would be willing to give up what I think is ideal to settle for something most commonly used (why I use semver when working in JavaScript). I'm not sure what the most common versioning scheme there is but at least anecdotally it seems fairly similar to semver or at least a subset of semver.