Is there any reason a new public project being started, if given the choice (e.g., not constrained by their company), would use something other than Semver? Are there competing methodologies, i.e., Semver has not been widely accepted yet?
This question arises because a very well known package that I use updated from 3.2 to 3.3. I blindly updated, thinking this could only add new APIs, not break old APIs. And to my surprise, 3.3 deleted some deprecated APIs. Checking their versioning, it did not state what "system" they use.
So, should we assume Semver is the default for [most/all] Github projects?
Edit2: I think this debate greatly depends on whether the software is a library or an end application (the user is sitting in front of it interacting with it). My original intention was to discuss the former. That is, if the code can be a dependency in other code. Non-semver libraries make it very hard to know whether it is safe to download a newer version of the library and depend on it. In contrast, I don't care what something like the version Firefox is because you aren't using it as a library, you're using it as an end application.