Release version scheme problematic with WiX about meme-box HOT 2 OPEN

many companies use "YEAR.SomeSubVersion.SomeFix" it feels a bit like WiX's Fault xD

hmm using 1.2022.1.1 would also look meh, is there any other allowed syntaxes which we can combine in? just for that builder

from meme-box.

Actually, I personally see a date as version scheme extremely rarely. Most software seems to have migrated to Semantic Versioning at some point.

Not saying your versioning scheme is wrong. Just SemVer became so dominant, that most tools expect a SemVer compatible version string. Technically, 2022 as major version is a SemVer valid string, but it's not SemVer compliant in the sense of when to bump specific version parts.

So I can kinda understand that WiX has a limit there (although, they don't really need to), because it's unusual for a typical SemVer major version to ever be that high.

I totally understand that SemVer is a bit more tricky for applications. For libraries, it's easy, patch for bugfixes, minor for any API compatible changes or additions, and major for any breaking API changes. Although even there, sometimes there are breaking changes without actually changing the API (like internal changes that modify the behavior of the library, thus changing the outcome despite the same API).

And for applications it's rather arbitrary. Sure patch bumps for bugfixes again, and mostly minor version bumps for regular releases, but when to bump the major version. Most applications seem to bump the major version for rather big revamps of the app or really large new features.

In the end, it's totally up to you. Just saying, you could just go with a regular SemVer instead of a date encoded in a SemVer.

from meme-box.