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

Merge pull request #1170 from kubernetes/jpbetz-patch-1 

Automatic merge from submit-queue.

Clarify how milestone should be set for cherrypicks
This commit is contained in:
Kubernetes Submit Queue 2017-10-24 02:37:48 -07:00 committed by GitHub
parent 6dd7c5e032 6b5ed4cd95
commit 0671ce70d9
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. To get a PR merged to the release branch, first ensure the following labels
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
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.