From 0a6008f4e5a842538327fb722a7610e6a8050e93 Mon Sep 17 00:00:00 2001 From: Jonathan Ringer Date: Fri, 4 Jun 2021 09:13:28 -0700 Subject: [PATCH] doc/manual: Add backport criteria --- .github/CONTRIBUTING.md | 3 ++- doc/contributing/submitting-changes.chapter.md | 11 +++++++++++ 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index cc1a6632ac4..159b9f84348 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -65,7 +65,8 @@ Anything that does not cause user or downstream dependency regressions can be ba - New Packages / Modules - Security / Patch updates - 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 diff --git a/doc/contributing/submitting-changes.chapter.md b/doc/contributing/submitting-changes.chapter.md index 97b32c15df1..29b8ec493e7 100644 --- a/doc/contributing/submitting-changes.chapter.md +++ b/doc/contributing/submitting-changes.chapter.md @@ -269,3 +269,14 @@ Other examples of reasons are: - Previously the build would fail due to, e.g., `getaddrinfo` not being defined - The previous download links were all broken - 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`)