This is an automated email from the ASF dual-hosted git repository.
rzo1 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 f0a8b453b Fixing error on release notes (#3671)
f0a8b453b is described below
commit f0a8b453b54c4b673432314b90f7b9ce7dbdbc0c
Author: reiabreu <[email protected]>
AuthorDate: Thu Jul 18 15:04:58 2024 +0100
Fixing error on release notes (#3671)
* Update RELEASING.md
* Update RELEASING.md
---
RELEASING.md | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/RELEASING.md b/RELEASING.md
index 3ee3bd78a..7d4be9b7f 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -60,9 +60,8 @@ In this way, you create a new release line and then you can
create PATCH version
2. Run `mvn release:prepare -P dist,rat,externals,examples` followed `mvn
release:perform -P dist,rat,externals,examples`.
This will create all the artifacts that will eventually be available in maven
central. This step may seem simple,
but a lot can go wrong (mainly flaky tests). Note that this will create and
push two commits with the commit message
-starting with "[maven-release-plugin]" and it will also create and publish a
git tag, e.g. `v2.6.0`.
-> [!WARNING]
-> The full build can take up to 30 minutes to be completed
+starting with "[maven-release-plugin]" and it will also create and publish a
git tag, e.g. `v2.6.0`. Note: the full build can take up to 30 minutes to
complete.
+
4. Once you get a successful maven release, a “staging repository” will be
created at http://repository.apache.org
in the “open” state, meaning it is still writable. You will need to close it,
making it read-only. You can find more
