News for hackers. Stuff that matters.
Re:Code that will break in Python 4 by plorkyeran on Tuesday January 12, 2016 @12:42PM (#10888889)
There were a lot of projects informally using what semver defined, but there were also a lot of other popular versioning schemes. Odd minor = unstable version, even minor = stable version used to be pretty popular and is still used by a few projects.

The main thing that helped make SemVer the default assumption was package managers that baked it into the dependency resolution, as until then a project's versioning scheme really didn't matter very much to the users of the project as long as it wasn't completely incomprehensible.

Re:Code that will break in Python 4 by jrochkind1 on Tuesday January 12, 2016 @12:59PM (#10889040)
Well, baking it into dependency resolution is a response to the fact that figuring out if there were breaking changes in any given update becomes intractable as your dependency tree/graph gets large (and multi-levelled), when each dependency uses it's own versioning scheme, no matter how comprehensible they are individually.