This is an automated email from the ASF dual-hosted git repository.
lukaszlenart pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/struts-site.git
The following commit(s) were added to refs/heads/main by this push:
new 6dd1a82ee3 docs: recommend a week-long test period between the test
build and the vote (#373)
6dd1a82ee3 is described below
commit 6dd1a82ee38cc4e2882518e8476d6620f8c0110e
Author: Lukasz Lenart <[email protected]>
AuthorDate: Sun Nov 8 18:47:47 2026 +0100
docs: recommend a week-long test period between the test build and the vote
(#373)
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 <[email protected]>
---
source/release-guidelines.md | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/source/release-guidelines.md b/source/release-guidelines.md
index 7320c4b899..bc2a20333c 100644
--- a/source/release-guidelines.md
+++ b/source/release-guidelines.md
@@ -304,9 +304,15 @@ The rest of this phase is paperwork:
- Send a `[TEST]` mail to `[email protected]` and
`[email protected]` announcing that the
build is available, and give people time to test the actual bits.
+The test period is the release manager's call. A week is the recommended
length: it gives users
+time to run the staged bits against their own applications and report problems
while they can
+still be fixed with a re-cut rather than a follow-up release. A shorter period
is a legitimate
+choice when circumstances call for it, not a violation.
+
## Phase 4 — Vote
-Post a release/quality vote to the dev list and only the dev list.
+Open the vote once the test period is over. Post a release/quality vote to the
dev list and only
+the dev list.
```
To: [email protected]
