3 ms·

I think this is a nice way to clarify the different use cases for version numbers: - SemVer is a communication tool for when an author needs to tell a potentia

I think this is a nice way to clarify the different use cases for version numbers: - SemVer is a communication tool for when an author needs to tell a potential user what to expect from a new version. - TrunkVer is an auditing/engineering tool for when you need to give a unique identifier to a version for technical reasons. I think this page is a nice codification of a useful practice, but it does itself a disservice by positioning itself against SemVar and claiming to be a "drop-in" replacement.

nine_k 2y ago
It's a "drop-in" replacement in the sense that it's compatible with the format and with the rough semantics of SemVer. That is, if your libraries / packages all use SemVer, but the final executable / image uses TrunkVer, the latter does not need to be special-cased. TrunkVer gives a stream of "major versions" that's strictly increasing and all incompatible, and uses non-version fields to convey useful info. All SemVer-based tools will accept a TrunkVer value and do the right thing (that is, always prefer the newest build).
spacechild1 2y ago
> but it does itself a disservice by positioning itself against SemVar I didn't read it like that at all!