diff options
| author | eduartua <eduartua@gmail.com> | 2019-01-29 11:03:22 -0600 |
|---|---|---|
| committer | eduartua <eduartua@gmail.com> | 2019-01-29 11:03:22 -0600 |
| commit | 3368adb2cc68e206bb2bb8cdbe92fe39b648e60b (patch) | |
| tree | 6550b7dbd4f7f8477aec72adeabbaba140bf4ff4 /contributors/guide/release-notes.md | |
| parent | ca79d659de6460b8268ff4ab87f04654482ad9bc (diff) | |
/devel/sig-release folder created - file cherry-picks.md moved to /devel/sig-release - URLs updated
Diffstat (limited to 'contributors/guide/release-notes.md')
| -rw-r--r-- | contributors/guide/release-notes.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/guide/release-notes.md b/contributors/guide/release-notes.md index 655dff1c..81dca597 100644 --- a/contributors/guide/release-notes.md +++ b/contributors/guide/release-notes.md @@ -30,4 +30,4 @@ For pull requests that don't need to be mentioned at release time, use the `/rel 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. +Release notes apply to pull requests on the master branch. For cherry-pick pull requests, see the [cherry-pick instructions](/contributors/devel/sig-release/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. |