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

Merge pull request #7298 from dlipovetsky/note-cherry-pick-all-supported-release-branches 

docs: Ask for cherry-picks to be made against all supported release branches
This commit is contained in:
Kubernetes Prow Robot 2023-05-22 00:02:21 -07:00 committed by GitHub
parent b7d0a3810c 457d644e7d
commit e071228147
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -76,7 +76,13 @@ 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.
### Before you begin
- Plan to initiate a cherry-pick against _every_ supported release branch. If you decide to skip some release branch, explain your decision in a comment to the PR being cherry-picked.
- Initiate cherry-picks in order, from newest to oldest supported release branches. For example, if 1.27 is the newest supported release branch, then, before cherry-picking to 1.25, make sure the cherry-pick PR already exists for in 1.26 and 1.27. This helps to prevent regressions as a result of an upgrade to the next release.
### Steps
- Run the [cherry pick script][cherry-pick-script]