doc/manual: Add backport criteria

This commit is contained in:
Jonathan Ringer 2021-06-04 09:13:28 -07:00 committed by Jonathan Ringer
parent 9d350d84c1
commit 0a6008f4e5
2 changed files with 13 additions and 1 deletions

View file

@ -65,7 +65,8 @@ Anything that does not cause user or downstream dependency regressions can be ba
- New Packages / Modules - New Packages / Modules
- Security / Patch updates - Security / Patch updates
- Version updates which include new functionality (but no breaking changes) - Version updates which include new functionality (but no breaking changes)
- Software which is always meant to be at it's latest. (E.g. `spotify`, `steam`, or `discord`) - Services which require a client to be up-to-date regardless. (E.g. `spotify`, `steam`, or `discord`)
- Security critical applications (E.g. `firefox`)
## Generating 21.11 Release Notes ## Generating 21.11 Release Notes

View file

@ -269,3 +269,14 @@ Other examples of reasons are:
- Previously the build would fail due to, e.g., `getaddrinfo` not being defined - Previously the build would fail due to, e.g., `getaddrinfo` not being defined
- The previous download links were all broken - The previous download links were all broken
- Crash when starting on some X11 systems - Crash when starting on some X11 systems
#### Acceptable backport criteria
The stable branch does have some changes which cannot be backported. Most notable are breaking changes. The desire is to have stable users be uninterrupted when updating packages.
However, many changes are able to be backported, including:
- New Packages / Modules
- Security / Patch updates
- Version updates which include new functionality (but no breaking changes)
- Services which require a client to be up-to-date regardless. (E.g. `spotify`, `steam`, or `discord`)
- Security critical applications (E.g. `firefox`)