kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7272 from dlipovetsky/note-cherry-picking-order 

docs: Ask for cherry-picks to be made in order from newest to oldest releases
This commit is contained in:
Kubernetes Prow Robot 2023-05-15 01:51:28 -07:00 committed by GitHub
parent 0cbf136e32 d8b001ac7e
commit d9c7d8f5a3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
contributors/devel/sig-release/cherry-picks.md
View File

@ -76,6 +76,8 @@ patch release branches.
## Initiate a Cherry Pick
Note: Before initiating a cherry-pick to a release branch, make sure the fix is available in every _newer_ release branch. For example, if 1.27 is the most recent release branch, then, before cherry-picking to 1.25, make sure the fix is already in 1.26 and 1.27. This helps to prevent regressions as a result of an upgrade to the next release.
- Run the [cherry pick script][cherry-pick-script]
This example applies a master branch PR #98765 to the remote branch