Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-06-05 13:39:17 -04:00
Code Issues Projects Releases Packages Wiki Activity

Clarify release number usage

Browse source
This commit is contained in:
Andrew David Wong 2022-07-04 20:58:37 -07:00
parent f49b630d5e
commit add0ebf529
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
1 changed files with 5 additions and 2 deletions

7
developer/releases/version-scheme.md
View file

@ -12,8 +12,11 @@ title: Version scheme
The Qubes OS Project uses the [semantic versioning](https://semver.org/) The Qubes OS Project uses the [semantic versioning](https://semver.org/)
standard. Version numbers are written as `<major>.<minor>.<patch>`. When standard. Version numbers are written as `<major>.<minor>.<patch>`. When
`<patch>` is zero, it is often omitted as a matter of convention, e.g., `4.1` is `<patch>` is omitted (e.g., `4.1`), it is usually either because `<patch>` is
short for `4.1.0`. zero (as in `4.1.0`) or because we are referring to a specific minor release
irrespective of any particular patch release within it. Similarly, the major
release number alone (e.g., `R4`) is sometimes used to refer to an entire
release series inclusive of all minor and patch releases within it.
In general, patch releases are for backward-compatible bug fixes, minor In general, patch releases are for backward-compatible bug fixes, minor
releases are for backward-compatible enhancements and new features, and major releases are for backward-compatible enhancements and new features, and major