5 ms·
SemVer is a relatively recent proposal that the vast majority of software does not follow. Calling the three parts of a three-part version “major”, “minor” and
by umanwizard 5y ago
SemVer is a relatively recent proposal that the vast majority of software does not follow. Calling the three parts of a three-part version “major”, “minor” and “patch” is a SemVer thing, not a universal standard.
- 101011 5y agoWorth calling out here that SemVer has been around for a decade now, so "recent" is relative
- rtsil 5y agoFor some of us, that is recent.
- JimDabell 5y agoSemVer did not introduce major / minor / patch, that was standard usage in free and open source software for decades beforehand. Example from 20 years ago: > The most popular version numbering scheme stems from the <major>.<minor>.<patchlevel> scheme — https://ask.slashdot.org/story/01/01/05/0054230/version-numbering-schemes https://ask.slashdot.org/story/01/01/05/0054230/version-numb... Example from 1997: > Python versions are numbered A.B.C or A.B. A is the major version number -- it is only incremented for major changes in functionality or source structure. B is the minor version number, incremented for less earth-shattering changes to a release. C is the patchlevel -- it is incremented for each new patch release. — https://web.archive.org/web/19970501012343/http://www.python.org:80/doc/FAQ.html#1.12 https://web.archive.org/web/19970501012343/http://www.python...
- umanwizard 5y agoFair enough, you’re right that it’s more widespread than just SemVer (though IMO still not an ironclad standard)
- wongarsu 5y agoThere's also Windows with it's A.B.C.D or major.minor.patch.build version scheme. Not sure how far back that goes, but it clearly predates semver as well.