github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-30 23:15:14 +00:00
Code Issues Projects Releases Wiki Activity

Update pull request and cherrypick docs for release notes to more accurately reflect current process.

Browse Source
This commit is contained in:
David McMahon 2016-05-02 17:35:10 -07:00
parent bacb12a112
commit 8c15651ff2
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/devel/cherry-picks.md
View File

@ -42,14 +42,12 @@ depending on the point in the release cycle.
1. Cherrypicks are [managed with labels and milestones] 1. Cherrypicks are [managed with labels and milestones]
(pull-requests.md#release-notes) (pull-requests.md#release-notes)
1. All label/milestone accounting happens on PRs on master. There's nothing to 1. To get a PR merged to the release branch, first ensure the following labels
do on PRs targeted to the release branches. are on the original **master** branch PR:
1. When you want a PR to be merged to the release branch, make the following * An appropriate milestone (e.g. v1.3)
label changes to the **master** branch PR: * The `cherrypick-candidate` label
* Remove release-note-label-needed 1. If `release-note-none` is set on the master PR, the cherrypick PR will need
* Add an appropriate release-note-(!label-needed) label to set the same label to confirm that no release note is needed.
* Add an appropriate milestone
* Add the `cherrypick-candidate` label
1. `release-note` labeled PRs generate a release note using the PR title by 1. `release-note` labeled PRs generate a release note using the PR title by
default OR the release-note block in the PR template if filled in. default OR the release-note block in the PR template if filled in.
* See the [PR template](../../.github/PULL_REQUEST_TEMPLATE.md) for more * See the [PR template](../../.github/PULL_REQUEST_TEMPLATE.md) for more