2 ms·
SemVer is working fine, you just need to face up to the real impact of a change on clients, not what you wish was the impact of the change. If a change breaks c
by jameshart 12y ago
SemVer is working fine, you just need to face up to the real impact of a change on clients, not what you wish was the impact of the change. If a change breaks clients who rely on buggy behavior, you need to bump a version, not a patch number.
- cortesoft 12y agoThis may be true, but in practice (as pointed out in the article), EVERYTHING can potentially be a breaking change (http://xkcd.com/1172/ http://xkcd.com/1172/). Since this is the case, you either need to always bump the version number (rendering the patch number useless), or bump the patch number but then have to wait for the bug reports to come in... once you get one bug report stating your patch broke someone's code, you would bump the version number... this doesn't seem practical, however.