This is an automated email from the ASF dual-hosted git repository.
reiabreu 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 80488902b Revise release instructions for storm-docker
80488902b is described below
commit 80488902b33c1db5bf58b17fa49f656e34a82769
Author: reiabreu <[email protected]>
AuthorDate: Sun Jun 28 14:45:45 2026 +0100
Revise release instructions for storm-docker
Updated release process to include Docker release steps and example PR.
---
RELEASING.md | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/RELEASING.md b/RELEASING.md
index 0e9edb099..cc51ac4b5 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -209,7 +209,9 @@ the site as described in the storm-site README to publish
the site.
10. Create a release on [GitHub](https://github.com/apache/storm/releases).
Generate the release notes with the GitHub tooling.
-11. Post, promote, celebrate. ;) Annoucement email can be sent to
[email protected] using the following template:
+11. 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
[...]
+
+12. Post, promote, celebrate. ;) Annoucement email can be sent to
[email protected] using the following template:
```agsl
Subject: [ANNOUNCE] Apache Storm [VERSION] Released
