4 ms·
Versioning is hard. Some people might claim that product A is better then product B because it has a higher version. Or they are getting annoyed by "lack of pro
by z3t4 8y ago
Versioning is hard. Some people might claim that product A is better then product B because it has a higher version. Or they are getting annoyed by "lack of progress" of a semver not having major releases (breaking changes) often enough. People read too much into the version nr. Making a new version might be a way to get some news buzz.
- benj111 8y agoThat isn't versioning per se, that's just branding and marketing and bike shedding. Not that I disagree with your point though.
- fendy3002 8y agoOn the other hand it's very useful for software libraries to detect breaking change. Lately I've found that node 8.14 added header size restriction that produce bugs, where it would've been easier if they just push to v10 instead. However talking about kernel maybe it isn't that much needed unless significant feature and breaking changes introduced.
- Osiris 8y agoThat change was to fix a vulnerability, hence why it was made to the LTS version. A flag was later added to make it customizable (after they realized it broke stuff).
- htfy96 8y agoThe problem is what is a breaking/major change for kernel? Is it referring to user-space API? The kernel ABI? Or the driver functionality/ABI?