3 ms·
What is the social contract of semver, as a library consumer? If either the patch or minor versions change, I should not care since everything is backwards comp
by joppy 6y ago
What is the social contract of semver, as a library consumer? If either the patch or minor versions change, I should not care since everything is backwards compatible. But if the major version changes, all bets are off. This seems like almost no contract at all.
It seems to me that this same information could be communicated by combining the minor and patch versions into one number, and changing the name of the library rather than changing the major version number.
- sixstringtheory 6y agoI like having the patch number set apart. I frequently run into bugs with dependencies where the first thing I check is if they've released a patch, so I can try that to fix the bug before digging any deeper. Muddle that with minor revisions and that information is lost. Minor revisions, in addition to signaling new functionality, also signal the possibility of the introduction of new bugs.
- joppy 6y agoSo both patch versions and minor versions signal the possibility of introduction of new bugs - is there a point to separating them?