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

Clarify release-note label requirement for non-master PRs.

Browse Source
This commit is contained in:
David McMahon
2016-04-07 17:14:13 -07:00
parent 2912fcc3ba
commit a71cb19867
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/devel/pull-requests.md
View File

@@ -86,7 +86,7 @@ This section applies only to pull requests on the master branch.
The only exception to these rules is when a PR is not a cherry-pick and is The only exception to these rules is when a PR is not a cherry-pick and is
targeted directly to the non-master branch. In this case, a `release-note-*` targeted directly to the non-master branch. In this case, a `release-note-*`
label is optional (and not enforced). label is required for that non-master PR.
### Reviewing pre-release notes ### Reviewing pre-release notes

2
docs/proposals/release-notes.md
View File

@@ -121,7 +121,7 @@ will be collected from that cherry-pick PR.
The only exception to this rule is when a PR is not a cherry-pick and is The only exception to this rule is when a PR is not a cherry-pick and is
targeted directly to the non-master branch. In this case, a `release-note-*` targeted directly to the non-master branch. In this case, a `release-note-*`
label is optional (and not enforced). label is required for that non-master PR.
1. New labels added to github: `release-note-none`, maybe others for new release note categories - see Layout section below 1. New labels added to github: `release-note-none`, maybe others for new release note categories - see Layout section below
1. A [new munger](https://github.com/kubernetes/kubernetes/issues/23409) that will: 1. A [new munger](https://github.com/kubernetes/kubernetes/issues/23409) that will: