This is an automated email from the ASF dual-hosted git repository.
jbertram pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-artemis.git
The following commit(s) were added to refs/heads/main by this push:
new 2a029cc717 NO-JIRA more release doc updates for re-spin
2a029cc717 is described below
commit 2a029cc717785be9c5f750b4521549fac693f113
Author: Justin Bertram <[email protected]>
AuthorDate: Mon Jul 14 15:11:28 2025 -0500
NO-JIRA more release doc updates for re-spin
---
RELEASING.adoc | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/RELEASING.adoc b/RELEASING.adoc
index 24377d101e..3d8e056f8e 100644
--- a/RELEASING.adoc
+++ b/RELEASING.adoc
@@ -364,7 +364,8 @@ Here's my +1
=== What if the vote fails?
-If the vote fails then you'll need to revert the two commits from the Maven
release process and delete the tag so the issues with the release can be fixed
and the release can be re-tagged.
+If the vote fails then you'll need clean up the previous release, fix the
issue(s), and re-spin the release.
+Cleaning up includes the following:
* The Maven release process creates 2 commits - one for preparing the release
and another for preparing the "next development iteration."
Here's an example of these commits as presented by `git log`:
@@ -421,6 +422,16 @@ git tag --delete 2.42.0
git push --delete apache 2.42.0
----
+* Delete the resources from Subversion created <<stage-the-release,here>>,
e.g.:
++
+[,console]
+----
+svn delete 2.42.0
+svn commit
+----
+
+* Drop the staging repository that was closed
<<close-the-staging-repository,here>>.
+
* Correct the issue with the release and proceed with the
<<prepare-maven-release,Maven release process>> once more.
== Send Result Email
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
