I've always thought of semver as documenting common sense: fix bugs often, add features when possible, and don't break the public API unless you have to. If al

I've always thought of semver as documenting common sense: fix bugs often, add features when possible, and don't break the public API unless you have to. If all projects strictly followed semver, we wouldn't have this debate. But it's not semver's fault that some developers ignore common sense.