An early draft of an alternate system to semantic versioning (semver) that I think is more useful in practice for both package maintainers (who don't want to evaluate every change for meaning, and want to be able to maintain large releases) and package contributors (who want to know what the maintenance period is)
Pragmatic versioning reflects more closely what many mature projects do in practice. Feedback welcome!
It basically just says that version numbers are meaningless and purely marketing. "Pragmatic" yes, but in need of standardization, no. The project comes across almost as a satire, so its odd for you to treat it as serious here.
Honestly, this is all too often how versions actually get used - that's what makes it feel like satire. But there's nothing wrong with admitting that the ideal of Semantic misses the mark, looking at real world usage, and saying "Okay, maybe we should formalize that in some way." I can see that being useful, especially if people are able to say "We use PragVersion rather than Semantic" to communicate the reality, rather than saying "We use Semantic" when they are, in fact, using Prag.
Pragmatic versioning reflects more closely what many mature projects do in practice. Feedback welcome!