3 ms·
This is called explicit versioning [1]. But in my opinion the correct fix is the one suggested in this comment: https://news.ycombinator.com/item?id=19138143 h
by eslaught 8y ago
This is called explicit versioning [1].
But in my opinion the correct fix is the one suggested in this comment: https://news.ycombinator.com/item?id=19138143 https://news.ycombinator.com/item?id=19138143
Windows is a great example: the number behind the name (7, 8, 8.1, 10, etc.) is just marketing gobbledygook. It doesn't even have to be a number (XP, etc.). The real version number of Windows is hidden from regular users---though they don't follow semver so I'm not sure it has much value per se. But they could plausibly adopt semver and regular users wouldn't need to know.
Let the marketing people choose the branding and the developers choose the version numbers. Keep those concerns separate, don't force them to be conflated.
[1]: https://medium.com/sapioit/why-having-3-numbers-in-the-version-name-is-bad-92fc1f6bc73c https://medium.com/sapioit/why-having-3-numbers-in-the-versi...
- wutbrodo 8y agoYea I don't get why you can't do this already, effectively. Just hide the real semver in the place it'll be consumed, with a comment tying it to the branded version if you want to reduce confusion.
- charrondev 8y agoBy numbers NPM is probably the biggest ecosystem using semver but the config files are JSON which don’t allow comments. Bit of a PITA generally but also makes this tougher to do consistently.