Repository navigation
docs: recommend a week-long test period between the test build and the vote - #373
Merged
Merged
Conversation
…e vote Phase 3 ended with "give people time to test the actual bits" and phase 4 started straight away, so the guidelines never said how long the test build stays open. A week is now the recommended length, with the decision left to the release manager. Co-Authored-By: Claude Mythos 5.1 <noreply@anthropic.com>
Member
Author
|
Companion skill change: apache/struts#2132 |
lukaszlenart
marked this pull request as ready for review
November 8, 2026 17:39
|
Staged site is ready at https://struts.staged.apache.org/ |
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.
The Release Guidelines said to "give people time to test the actual bits" after the
[TEST]mail and then moved straight to phase 4, without saying how long that time is. This adds a paragraph at the end of phase 3: a week is the recommended test period, the decision is the release manager's, and a shorter period is a legitimate choice rather than a violation. Phase 4 now opens with "once the test period is over".Companion change to the release skills in apache/struts (linked in the first comment).
🤖 Generated with Claude Code