docs: clarify release execution phases#41
Merged
Conversation
Reduce release confusion by making phase boundaries, version states, and post-release reopen work explicit in the central release docs. Constraint: release docs must preserve the canonical Version Management Policy while making execution order clear for operators. Rejected: add more isolated warnings | phase gates make the next valid action clearer than scattered cautions. Confidence: high Scope-risk: narrow Directive: when future release mistakes happen, update the relevant phase gate or state table first. Tested: git diff --check Not-tested: rendered documentation site
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.
Summary
developshould normally use matching internal-SNAPSHOTreferences.baseVersionadvancement plus emptysnapshotVersion, not checked-in*-SNAPSHOTversion bumps.Verification
git diff --check