diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2019-10-01 12:13:34 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-10-01 12:13:34 -0700 |
| commit | c4327600d50f4459817d5652263366160ebfe53e (patch) | |
| tree | f10ffebf700cd131adfc7bcf5f24ee93385edac0 | |
| parent | 0cbbef87b3811652e300235634d102edf6812da6 (diff) | |
| parent | fc51e717a939a6b1e3b264262cea5959277e3750 (diff) | |
Merge pull request #4127 from obitech/lightning_talk_contrib_docs
Add KubeCon lightning talk to release-notes docs
| -rw-r--r-- | contributors/guide/release-notes.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/contributors/guide/release-notes.md b/contributors/guide/release-notes.md index ee8bf8aa..0b3223c4 100644 --- a/contributors/guide/release-notes.md +++ b/contributors/guide/release-notes.md @@ -35,3 +35,7 @@ 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 patch release branches the automated cherry-pick pull requests process (see the [cherry-pick instructions](/contributors/devel/sig-release/cherry-picks.md)) should be followed. That automation will pull release notes from the master branch PR from which the cherry-pick originated. On a rare occasion a pull request on a patch release branch is not a cherry-pick, but rather is targeted directly to the non-master branch and in this case, a `release-note-*` label is required for that non-master pull request. + +## Related + +* [Behind The Scenes: Kubernetes Release Notes Tips & Tricks - Mike Arpaia, Kolide (KubeCon 2018 Lightning Talk)](https://www.youtube.com/watch?v=n62oPohOyYs) |