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

Clarify how milestone should be set for cherrypicks

This commit is contained in:
Joe Betz 2017-10-10 10:41:45 -07:00 committed by GitHub
parent da223908b7
commit 29c7f6cbe1
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -9,7 +9,7 @@ depending on the point in the release cycle.
1. Cherrypicks are [managed with labels and milestones](pull-requests.md#write-release-notes-if-needed) 1. Cherrypicks are [managed with labels and milestones](pull-requests.md#write-release-notes-if-needed)
1. To get a PR merged to the release branch, first ensure the following labels 1. To get a PR merged to the release branch, first ensure the following labels
are on the original **master** branch PR: are on the original **master** branch PR:
* An appropriate milestone (e.g. v1.3) * The `milestone` for the branch that you want to cherry-pick to (e.g. v1.7 if you want to backport your change in 1.7 branch)
* The `cherrypick-candidate` label * The `cherrypick-candidate` label
1. If `release-note-none` is set on the master PR, the cherrypick PR will need 1. If `release-note-none` is set on the master PR, the cherrypick PR will need
to set the same label to confirm that no release note is needed. to set the same label to confirm that no release note is needed.