diff options
| author | Joe Betz <jpbetz@google.com> | 2017-10-10 10:41:45 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-10-10 10:41:45 -0700 |
| commit | 29c7f6cbe15bc9246cccda8be049667b8de40334 (patch) | |
| tree | 33c536e78eefbe46e4fde960a3307d336bc6d297 | |
| parent | da223908b764900666bd7b19c0b65c6ab5b4e093 (diff) | |
Clarify how milestone should be set for cherrypicks
| -rw-r--r-- | contributors/devel/cherry-picks.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/devel/cherry-picks.md b/contributors/devel/cherry-picks.md index 43b32bdb..e1f60789 100644 --- a/contributors/devel/cherry-picks.md +++ b/contributors/devel/cherry-picks.md @@ -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. |