This is an automated email from the ASF dual-hosted git repository.
rabreu pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/storm.git
The following commit(s) were added to refs/heads/master by this push:
new 212b4702b Update release notes generation instructions
212b4702b is described below
commit 212b4702b24c3d0486234c43a0aaf12a34a75a1b
Author: reiabreu <[email protected]>
AuthorDate: Sun Oct 26 01:40:22 2025 +0100
Update release notes generation instructions
Added a reminder to check milestone assignments for merged pull requests
before generating release notes.
---
RELEASING.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/RELEASING.md b/RELEASING.md
index dd55d85fc..c9ff2db22 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -85,7 +85,9 @@ popd
6. Create a directory in the dist svn repo for the release candidate:
https://dist.apache.org/repos/dist/dev/storm/apache-storm-x.x.x-rcx
-7. Run `dev-tools/release_notes.py` for the release version, piping the output
to a RELEASE_NOTES.html file. Move that file to the svn release directory, sign
it, and generate checksums, e.g.
+7. Before generating the release notes, please double check if all merged pull
requests for the version being released are assigned the milestone in question.
They won't be placed in the release notes otherwise
+
+8. Run `dev-tools/release_notes.py` for the release version, piping the output
to a RELEASE_NOTES.html file. Move that file to the svn release directory, sign
it, and generate checksums, e.g.
```bash
export GITHUB_TOKEN=MY_PERSONAL_ACCESS_TOKEN_FOR_GI
python3 dev-tools/release_notes.py <id-of-the-github-milestone> >
RELEASE_NOTES.html
