docs(release): record ATR's move to beta, and decouple the policy from it - #1181
Draft
potiuk wants to merge 1 commit into
Draft
docs(release): record ATR's move to beta, and decouple the policy from it#1181potiuk wants to merge 1 commit into
potiuk wants to merge 1 commit into
Conversation
…m it ATR has moved from alpha to beta. Reported by @dave2wave in apache#1157, which this supersedes with the full sweep — the runbook alone stated the status in four places, and three other documents repeated it. The substantive change is not the word. Several passages made Magpie's hybrid stance a *consequence* of ATR's maturity — "because ATR is still alpha, Magpie does not yet let it host or publish releases" — so a status change appeared to move the policy on its own. It does not. Whether ATR hosts and publishes Magpie's releases is a PMC decision, and the config already said so: full adoption had two preconditions, a ratification vote on dev@ *and* ATR moving beyond alpha. The second is now met. So the docs now state the maturity fact, state the policy as a governance decision, and say plainly that the ratification vote is the only remaining blocker. The policy itself is unchanged. Two alpha mentions deliberately survive. `release-management-config.md` names it as the precondition that has now been met, and the 0.1.0 retrospective in `manual-release-process.md` records friction from a release where ATR genuinely was alpha — now marked "alpha at the time" so a later reader does not misread it as current. Follow-up issue to be opened asking which alpha-era assumptions still hold. Generated-by: Claude Code (Opus 5)
potiuk
marked this pull request as draft
September 9, 2026 00:23
This was referenced Sep 9, 2026
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
1 participant
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.
Supersedes #1157 by @dave2wave, who flagged that ATR has moved from alpha to beta and that the playbook needed updating. That PR marked one spot; this does the full sweep — the ATR runbook alone stated the status in four places, and three other documents repeated it.
The substantive change is not the word
Several passages made Magpie's hybrid stance a consequence of ATR's maturity:
Read literally, that says the policy moves when the status moves. It does not. Whether ATR hosts and publishes Magpie's releases is a PMC decision — and
release-management-config.mdalready said so, listing two preconditions for full adoption: a ratification vote ondev@, and ATR moving beyond alpha.The second is now met. So the docs now state the maturity fact, state the policy as a governance decision, and say plainly that the ratification vote is the only remaining blocker.
The policy itself is unchanged.
release_dist_backend = svnpubsubandrelease_vote_backend = atrstay exactly as they are.Two alpha mentions deliberately survive
release-management-config.mdnames alpha as the precondition that has now been met.manual-release-process.mdrecords friction from a release where ATR genuinely was alpha. Rewriting it would falsify the record, so it is now marked "alpha at the time" instead.Open questions
#1182 asks @dave2wave and @sbp which alpha-era assumptions still hold under beta — client/API stability, which host to target, the hosting-trust argument, dual staging, and the
[VOTE]template. Whatever comes back gets folded in here before this leaves draft.🤖 Generated with Claude Code
https://claude.ai/code/session_015qpVgY8ADkD9c7vYZk5imP