diff options
| author | Victor Marmol <vmarmol@google.com> | 2015-07-08 14:37:59 -0700 |
|---|---|---|
| committer | Victor Marmol <vmarmol@google.com> | 2015-07-08 14:37:59 -0700 |
| commit | ce319d424c06c915af4e7e0ce463ec8adbe086de (patch) | |
| tree | 2f866cfbb69f642e7b56cc7d3d8654a6a199b6e2 | |
| parent | 7daae9eda4c829afc1f7dcdf2d84102903785947 (diff) | |
| parent | 2b8e318ccafb353dc06bb7066ccb8671591bbaba (diff) | |
Merge pull request #10887 from alex-mohr/release-notes2
Update release notes tool and documentation
| -rw-r--r-- | making-release-notes.md | 14 |
1 files changed, 9 insertions, 5 deletions
diff --git a/making-release-notes.md b/making-release-notes.md index ffccf6d3..5d08ac50 100644 --- a/making-release-notes.md +++ b/making-release-notes.md @@ -2,17 +2,21 @@ This documents the process for making release notes for a release. ### 1) Note the PR number of the previous release -Find the PR that was merged with the previous release. Remember this number +Find the most-recent PR that was merged with the previous .0 release. Remember this as $LASTPR. _TODO_: Figure out a way to record this somewhere to save the next release engineer time. -### 2) Build the release-notes tool +Find the most-recent PR that was merged with the current .0 release. Remeber this as $CURRENTPR. + +### 2) Run the release-notes tool ```bash -${KUBERNETES_ROOT}/build/make-release-notes.sh <pr-number-from-1> +${KUBERNETES_ROOT}/build/make-release-notes.sh $LASTPR $CURRENTPR ``` ### 3) Trim the release notes -This generates a list of the entire set of PRs merged since the last release. It is likely long -and many PRs aren't worth mentioning. +This generates a list of the entire set of PRs merged since the last minor +release. It is likely long and many PRs aren't worth mentioning. If any of the +PRs were cherrypicked into patches on the last minor release, you should exclude +them from the current release's notes. Open up ```candidate-notes.md``` in your favorite editor. |