snlavaise/pmaports-rtwo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: allow TCs to backport to stable releases

Browse Source 
Relates https://gitlab.postmarketos.org/postmarketOS/postmarketos/-/issues/131

Signed-off-by: Pablo Correa Gómez <pabloyoyoista@postmarketos.org>
Part-of: <https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/7625>
This commit is contained in:
Pablo Correa Gómez
2025-12-25 23:32:43 +00:00
committed by The Friendly Merge Bot
parent 57c75db149
commit 4e23818b18
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/approval-rules.md
+5 -6
View File
@@ -40,10 +40,9 @@ cases, before merging, in addition to the regular approvals, it is required to:
Backporting features from edge to stable is done at request of the MR author or Backporting features from edge to stable is done at request of the MR author or
package maintainer. All patches for stable branches must go through edge first package maintainer. All patches for stable branches must go through edge first
and get backported from there to get additional testing before they potentially and get backported from there to get additional testing before they potentially
breaks something in stable. The only exception are patches for failures that breaks something in stable, and should be tested in the MR too. The only
only happen on stable. exception are patches for failures that only happen on stable.
Only some members of the team are allowed to push to stable branches. To get a While backporting patches to stable, label the MR with the corresponding
patch backported to stable, label the MR with the corresponding `backport-to-v*` `backport-to-v*` label, and cherry-pick the commits with the `-x` option, to
label, and request a Core Contributor to cherry-pick it. Cherry-picking should make sure that the original commit is mentioned.
be done using `-x` option, to make sure that the original commit is mentioned.