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 History
- CHANGES
- 3.1.1
- 3.1.0
- 3.0.1
- 3.0.0
- 2.1.0
- 2.0.0
- 1.10.0
- 1.9.1
- 1.9.0
- 1.8.1
- 1.8.0
- 1.7.0
- 1.6.0
- 1.5.0
- 1.4.0
- 1.3.0
- 1.2.0
- 1.1.1
- 1.1.0
- 1.0.1
- 1.0.0
- 0.11.0
- 0.10.7
- 0.10.6
- 0.10.5
- 0.10.4
- 0.10.3
- 0.10.1
- 0.10.2
- 0.9.0
- 0.8.2
- 0.8.1
- 0.8.0
- 0.7.0
- 0.6
- 0.5.23
- 0.5.22
- 0.5.21
- 0.5.20
- 0.5.19
- 0.5.18
- 0.5.17
- 0.5.16
- 0.5.15
- 0.5.14
- 0.5.12
- 0.5.11
- 0.5.10
- 0.5.8
- 0.5.6
- 0.5.0
- CHANGES