Using pbr¶
- Features
- Usage
- Notes for Package maintainers
- Linux/Python Compatible Semantic Versioning 3.0.0
- Changes vs SemVer 2.0
- Summary
- Introduction
- Semantic Versioning Specification (SemVer)
- Why Use Semantic Versioning?
- FAQ
- How should I deal with revisions in the 0.y.z initial development phase?
- How do I know when to release 1.0.0?
- Doesn’t this discourage rapid development and fast iteration?
- If even the tiniest backwards incompatible changes to the public API require a major version bump, won’t I end up at version 42.0.0 very rapidly?
- Documenting the entire public API is too much work!
- What do I do if I accidentally release a backwards incompatible change as a minor version?
- What should I do if I update my own dependencies without changing the public API?
- What if I inadvertently alter the public API in a way that is not compliant with the version number change (i.e. the code incorrectly introduces a major breaking change in a patch release)
- How should I handle deprecating functionality?
- Does SemVer have a size limit on the version string?
- About
- License
- Compatibility Notes
- Release Notes
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.