Repository navigation
Conversation
Document staging, voting, publishing and announcing through ATR, on the website or from the atr command line. The SVN steps stay as the alternative. Release managers must pick one path per release and not mix them. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
ATR can fetch the vote email template from a URL. The new dev-tools/atr/start-vote-template.txt is the Storm template, built from ATR's default with the Storm specifics from RELEASING.md (Nexus staging repository, full and lite binaries, how to vote). It is excluded from RAT because it is sent as an email body. RELEASING.md explains the one-time ATR setting and how the website form and the command line use it. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
RELEASING.md keeps pointing at dev-tools/atr/start-vote-template.txt, which is added by that pull request. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
atrclient) 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 acceptsCHANGES,LICENSE,NOTICE,READMEandSECURITYat the top level, and the document says to acknowledge it.Vote email template: the one-time setup tells the release manager to point ATR's Start vote template URL at
dev-tools/atr/start-vote-template.txt. That file is added by Add the Storm vote email template for ATR #9265, which this PR depends on.Not verified: the commands come from the ATR documentation and the
atrclient'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