reiabreu opened a new pull request, #9264: URL: https://github.com/apache/storm/pull/9264
Adds ATR to the release process in `RELEASING.md`, for discussion. The existing SVN steps stay as the alternative. - **Pick one path:** a release manager uses ATR or SVN for a release, never both. The notes say where the paths diverge (staging, vote email, publishing, announcing) and what mixing them does. - **Website or command line:** every ATR step is documented for both. A new section covers the one-time setup (MFA, release manager designation, OpenPGP key, SSH key or personal access token, installing the `atr` client) and has a table of operations side by side. - **Steps with an ATR and an SVN variant:** staging the candidate (6, 9, 10), starting the vote (11, with `[CANDIDATE_URL]` and `[RELEASE_NOTES_URL]` placeholders in the sample email), resolving the vote, publishing, recording the Maven Central release, announcing, archiving, and cleaning up after a failed vote. - **Unchanged:** the Maven release, signing, checksums, release notes, and the Nexus staging repository. ATR does not do these. - **Expected ATR concern:** `RELEASE_NOTES.html: Unknown top level file`. ATR only accepts `CHANGES`, `LICENSE`, `NOTICE`, `README` and `SECURITY` at the top level, and the document says to acknowledge it. Not verified: the commands come from the ATR documentation and the `atr` client's help. They have not been run end to end for a Storm release, and ATR is in beta. This PR stays a draft until a release has gone through ATR and the PMC agrees to use it. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
