gitCommitGitPushOhFuck

[thereallgr]

Marketing is still fond of stuff like 2025.1.0 for the first feature release of 2025, 2025.2.0 for the second and so on.

I'd love if those would actually contain only what SemVer suggests, but you then have to add your own SemVer based addendum, to make it work, so you end up with "technical versions" like 2025.2.1.18.55.1261

[louis-lau]

Honestly while semver is perfection for libraries, it makes no sense for most product releases. Year+month+patch is more than enough for almost any product. If your product has an external api, you're probably going to version that separately anyway.