This is an automated email from the ASF dual-hosted git repository. reiabreu pushed a commit to branch releasing-close-milestone in repository https://gitbox.apache.org/repos/asf/storm.git
commit 26ad1004e1cf8b02ec2811a36ce6a14fe240e1ff Author: Rui Abreu <[email protected]> AuthorDate: Sun Sep 13 10:44:14 2026 +0100 RELEASING: add step to close the GitHub milestone after release Co-Authored-By: Claude Opus 4.8 <[email protected]> --- RELEASING.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index a2a4dbb40..71208debc 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -277,9 +277,11 @@ from Maven Central (or an internal mirror configured in `settings.xml`). 8. Create a release on [GitHub](https://github.com/apache/storm/releases). Generate the release notes with the GitHub tooling. -9. Create a new release for [Storm Docker](https://github.com/apache/storm-docker). Example of a version release [here](https://github.com/apache/storm-docker/commit/177a1534bf910c2271845f4eaedef7c040559fbc). After that is done, a PR to [docker-library](https://github.com/docker-library/official-images) must be submitted, so that the new docker-storm version is officially released. Example of such a PR is [here](https://github.com/docker-library/official-images/pull/21525#issuecomment-45 [...] +9. Close the milestone for the released version in GitHub. Go to the [milestones page](https://github.com/apache/storm/milestones), open the milestone matching the released version (e.g. `3.1.0`), and click **Close milestone**. Confirm it has no open issues first; move any still-open items to a later milestone before closing. -10. Post, promote, celebrate. ;) Announce the new release to [email protected], [email protected], and [email protected] (you must use your @apache.org email to post to [email protected]), using the following template: +10. Create a new release for [Storm Docker](https://github.com/apache/storm-docker). Example of a version release [here](https://github.com/apache/storm-docker/commit/177a1534bf910c2271845f4eaedef7c040559fbc). After that is done, a PR to [docker-library](https://github.com/docker-library/official-images) must be submitted, so that the new docker-storm version is officially released. Example of such a PR is [here](https://github.com/docker-library/official-images/pull/21525#issuecomment-4 [...] + +11. Post, promote, celebrate. ;) Announce the new release to [email protected], [email protected], and [email protected] (you must use your @apache.org email to post to [email protected]), using the following template: ```text Subject: [ANNOUNCE] Apache Storm [VERSION] Released
