From 8fdd2072eeaf393f76b40668a60b353abde8758f Mon Sep 17 00:00:00 2001 From: Eric Anderson Date: Wed, 15 May 2019 14:40:12 -0700 Subject: [PATCH] RELEASING.md: Document command to start making release notes It's fine if the command changes in the future, but we do want to start making the release notes earlier than later. --- RELEASING.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/RELEASING.md b/RELEASING.md index edff86529b..f72fba0cfe 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -94,6 +94,14 @@ would be used to create all `v1.7` tags (e.g. `v1.7.0`, `v1.7.1`). 7. Move items out of the release milestone that didn't make the cut. Issues that may be backported should stay in the release milestone. Treat issues with the 'release blocker' label with special care. +8. Begin compiling release notes. This produces a starting point: + + ```bash + $ echo "## gRPC Java $MAJOR.$MINOR.0 Release Notes" && echo && \ + git shortlog "$(git merge-base upstream/v$MAJOR.$((MINOR-1)).x upstream/v$MAJOR.$MINOR.x)"..upstream/v$MAJOR.$MINOR.x | cat && \ + echo && echo && echo "Backported commits in previous release:" && \ + git cherry -v v$MAJOR.$((MINOR-1)).0 upstream/v$MAJOR.$MINOR.x | grep ^- + ``` Tagging the Release -------------------