2 ms·
To a consumer a 1.0.0 may be more stable. At a 1.0.0 you expect the authors to not change the API for what ever the API is for the thing. Your interactions wit
by mfer 6y ago
To a consumer a 1.0.0 may be more stable.
At a 1.0.0 you expect the authors to not change the API for what ever the API is for the thing. Your interactions with the software have an expected level of stability and authors don't need to take into account prior to that.
Stable means no changing or firmly established. Once you tag a 1.0.0 you say that some things will no longer change. Hence, an element of stability.
- ryan_lane 6y agoNo, it means that anything within 1.0 won't change, but that 2.0.0 and above will include breaking changes from 1.0.0. That's the whole point. Semver versions don't imply general stability of the service, just stability of the interface within the major versions. If you're depending on the software in your dependencies, you can mark >1.0.0,<2.0.0 and if people are correctly doing semver, your software won't break. When you need to move to another major version, you'll need to ensure your usage hasn't broken with the change.