diff options
| author | guineveresaenger <guineveresaenger@gmail.com> | 2018-02-21 13:38:17 -0800 |
|---|---|---|
| committer | guineveresaenger <guineveresaenger@gmail.com> | 2018-02-22 14:42:13 -0800 |
| commit | 405849f487e10bbf24e2a952f9ff2e68f5bf5bf3 (patch) | |
| tree | 7a0c8df80ee1ce4fb9d2f2bdb2a8d4e4c798e99c /contributors/guide/release-notes.md | |
| parent | 66eb35601df6f472b5e2edf2edc24335dbca0593 (diff) | |
Release Notes: Title added; minor cleanup. Faster reviews tombstone added. Minor cleanup in pull-requests.md
Diffstat (limited to 'contributors/guide/release-notes.md')
| -rw-r--r-- | contributors/guide/release-notes.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/contributors/guide/release-notes.md b/contributors/guide/release-notes.md index 6015f12e..e9fcb4df 100644 --- a/contributors/guide/release-notes.md +++ b/contributors/guide/release-notes.md @@ -1,3 +1,5 @@ +# Adding Release Notes + On the kubernetes/kubernetes repository, release notes are required for any pull request with user-visible changes, such as bug-fixes, feature additions, and output format changes. To meet this requirement, do one of the following: @@ -28,8 +30,6 @@ For pull requests that don't need to be mentioned at release time, just write "N The `/release-note-none` comment command can still be used as an alternative to writing "NONE" in the release-note block if it is left empty. -To see how to format your release notes, view the kubernetes/kubernetes[pull request template](https://git.k8s.io/kubernetes/.github/PULL_REQUEST_TEMPLATE.md) for a brief example. pull request titles and body comments can be modified at any time prior to the release to make them friendly for release notes. - -Release notes apply to pull requests on the master branch. For cherry-pick pull requests, see the [cherry-pick instructions](contributors/devel/cherry-picks.md). The only exception to these rules is when a pull request is not a cherry-pick and is targeted directly to the non-master branch. In this case, a `release-note-*` label is required for that non-master pull request. +To see how to format your release notes, view the kubernetes/kubernetes [pull request template](https://git.k8s.io/kubernetes/.github/PULL_REQUEST_TEMPLATE.md) for a brief example. pull request titles and body comments can be modified at any time prior to the release to make them friendly for release notes. -Now that your release notes are in shape, let's look at how the pull request gets tested and merged.
\ No newline at end of file +Release notes apply to pull requests on the master branch. For cherry-pick pull requests, see the [cherry-pick instructions](contributors/devel/cherry-picks.md). The only exception to these rules is when a pull request is not a cherry-pick and is targeted directly to the non-master branch. In this case, a `release-note-*` label is required for that non-master pull request.
\ No newline at end of file |