...
- When a serious security issue arises, we should try to create a
#.#.#.1
branch on from the last GA release, and apply to that branch only
the security patch. - If the patch first applies to WebWorkXWork, or some other dependency, implore the other group to do the same, to avoid side-effects from other changes.
- If the release manager would like to "fast track" a vote, so as to make a security fix available quickly, the preferred procedure is to
Wiki Markup Include the term "fast-track" in the subject, as in {{\[VOTE\] Struts 2.0.9.1 quality (fast track)}}
- In the vote message, specify voting terms like:
The Struts #.#.#.1 test build is now available.
Release notes:
Distribution:
Maven 2 staging repository:
Once you have had a chance to review the test build, please respond with a vote on its quality:
Wiki Markup \[ \] Leave at test build \[ \] Alpha \[ \] Beta \[ \] General Availability (GA)
Everyone who has tested the build is invited to vote. Votes by PMC members are considered binding. A vote passes if there are at least three binding +1s and more +1s than -1s.
This is a "fast-track" release vote. If we have a positive vote after 24 hours (at least three binding +1s and more +1s than -1s), the release may be submitted for mirroring and announced to the usual channels.
Wiki Markup The website download link will include the mirroring timestamp parameter \[1\], which limits the selection of mirrors to those that have been refreshed since the indicated time and date. (After 24 hours, we \*must\* remove the timestamp parameter from the website link, to avoid unnecessary server load.) In the case of a fast-track release, the email announcement will not link directly to <download.cgi>, but to <downloads.html>, so that we can control use of the timestamp parameter.
Wiki Markup \[1\] <[http://apache.org/dev/mirrors.html#use|http://apache.org/dev/mirrors.html#use]>