Given a version number MAJOR.MINOR, increment the:
1. MAJOR version when you make incompatible API changes. 1. MINOR version when you make backwards-compatible changes.
First, I want to thank Semantic Versioning for giving the world a tool to manage compatibility in software dependencies.
SemVer treats releases with new features separately from releases with bug fixes. For dependency management, that distinction isn’t important: all that matters is backwards compatibility. “Fixed a bug” and “Added a feature” are both examples of “made the software better”, as long as you didn’t break something. SimVer is meant to address that difference.
SimVer is the same SemVer, with these modifications:
SimVer works best when bugs are relatively rare, when you release quickly/easily/safely, and when you don’t maintain many released branches.
Maybe. Why is this a problem?
I’m tempted to say that security fixes can be minor releases, even if they break compatibility. Thoughts?
The Simple Versioning specification is authored by Jay Bazuzi.
If you’d like to leave feedback, please tweet at me.