Bug versions are for bug fixes Minor versions are for non-api breaking changes (new functions, logic changes that allow for functions to be called the same way, etc...) Major versions are for API breaking changes (complete reworks of function namings)
I had a general understanding of what was happening but never really made the MAJOR.MINOR.BUG association. Probably something I could have figured out but just never had my noodle aimed at 'naming' it.
Stellaris is at 3.14.14 right now and is making the big jump to 4.0.0 in Q2 this year. So my mind made the "EW A WHOLE LOTTA STUFF THIS TIME!" rather then the "3.15 Hope I get this quality of life improvement" or "3.14.15...Prolly some fixes for something I haven't run into yet."
The important one is the major, because you have to be prepared for your code breaking when you update. At least with an api or framework you use, a game only if you're into modding i guess.
SemVer doesn't really apply to applications like games, since they don't typically have an API (other than a potential modding API) that breaks compatability. You could instead go for savegame compatability, but in some games (Stellaris included) they often break even among minor version updates. Besides, SemVer isn't really the ultimative standard when it comes to game versioning. See the plentiful MMOs that release version 1.1 -> 1.15 -> 1.2 instead of 1.1 -> 1.1.5 -> 1.2
Personally I'm a fan of either a more verbose versioning (e.g. "Update X [Hotfix Y]") or build number.
I worked a project where we had to add a fourth number, because people where getting into a panic about how often we were changing the major version. So version 1.2.3.4 was: 1.x.x.x was if all you did was install and configure, we've possibly done something that broke your config, take a look. X.2.x.x was if you did any programmatic extension, look to make sure we didn't change the apis you were using. X.x.3.x, hooray new features. X.x.x.4, we screwed something up, this fixes it.
Some of our internal libraries follow semver pretty strictly. People certainly take a double-take if that library has a version of 11.2.9 or something with a high major version like that.
Though a lot of these major changes are cleanup at this point - removal of redundant functions, renames of old mistakes everyone disliked and such (or, rather, removal of the compatibility layer during the rename) and such. Oftentimes, the deprecation notice/upgrade guide is "inline this one layer".
If you are a corporate entity 'MAJOR' may also mean 'IT IS A NEW FISCAL AND WE NEED A NEW VERSION OF OUR PRODUCT TO SELL SO PRESENT ALL THE MINOR UPDATES AND PATCHES SO FAR AS THE NEW MAJOR VERSION'
2.5k
u/Mallissin Mar 03 '25
I think this is actually a pretty reasonable system and I 1.0.000% support you.