You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ozone.apache.org by we...@apache.org on 2025/03/24 21:18:26 UTC
(ozone-site) branch HDDS-9225-website-v2 updated: HDDS-12674. Add cleanup for abandoned RC in RM guide (#139)
This is an automated email from the ASF dual-hosted git repository.
weichiu pushed a commit to branch HDDS-9225-website-v2
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
The following commit(s) were added to refs/heads/HDDS-9225-website-v2 by this push:
new 35bf6cdd HDDS-12674. Add cleanup for abandoned RC in RM guide (#139)
35bf6cdd is described below
commit 35bf6cdde1e1f4aca2825050cdb8b44d3733933c
Author: Doroszlai, Attila <64...@users.noreply.github.com>
AuthorDate: Mon Mar 24 22:18:22 2025 +0100
HDDS-12674. Add cleanup for abandoned RC in RM guide (#139)
---
docs/08-developer-guide/04-project/02-release-guide.md | 16 +++++++++++++++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git a/docs/08-developer-guide/04-project/02-release-guide.md b/docs/08-developer-guide/04-project/02-release-guide.md
index 01a9bf7e..7c48efc7 100644
--- a/docs/08-developer-guide/04-project/02-release-guide.md
+++ b/docs/08-developer-guide/04-project/02-release-guide.md
@@ -370,7 +370,21 @@ Send a vote email to the dev@ozone.apache.org mailing list. Include the followin
If no issues are found with the artifacts, let the vote run for 7 days. Review the [ASF wide release voting policy](https://www.apache.org/legal/release-policy.html#release-approval), and note the requirements for binding votes which can only come from PMC members. Sometimes responders will not specify whether their vote is binding. If in doubt check the [ASF committer index](https://people.apache.org/committer-index.html). Users whose group membership includes `ozone-pmc` can cast bindi [...]
-Once voting is finished, send an email summarizing the results (binding +1s, non-binding +1s, -1s, 0s) and, if the vote passed, indicate that the release artifacts will be published. If an issue is found with the artifacts, apply fixes to the release branch and repeat the steps starting from [Tag the Commit for the Release Candidate](#tag-the-commit-for-the-release-candidate) with the `$RC` variable incremented by 1 for all steps.
+Once voting is finished, send an email summarizing the results (binding +1s, non-binding +1s, -1s, 0s) and, if the vote passed, indicate that the release artifacts will be published.
+
+### If Release Candidate has Problems
+
+If an issue is found with the artifacts:
+
+1. Remove the abandoned release candidate from Subversion.
+
+ ```bash
+ svn delete -m "Abandon Ozone $VERSION RC$RC" https://dist.apache.org/repos/dist/dev/ozone/"$VERSION-rc$RC"
+ ```
+
+2. Discard the staging repository at https://repository.apache.org/#stagingRepositories
+3. Apply fixes to the release branch.
+4. Repeat the steps starting from [Tag the Commit for the Release Candidate](#tag-the-commit-for-the-release-candidate) with the `$RC` variable incremented by 1 for all steps.
## After-Vote
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@ozone.apache.org
For additional commands, e-mail: commits-help@ozone.apache.org