There's not an actual drop-dead date. Like merit, quality votes never expire.
The 72-hour clause just means that if we had 3 +1s by then, and nothing seemed awry, we might go ahead and announce it. Hey, elsewhere, I've been known to cast positive quality votes even weeks after the announcement, just as a matter of record. :) Even after we announce a quality grade, the grade is still subject to actual experience. If a serious issue were discovered later, we could change our votes and downgrade the quality, if appropriate. Likewise, we can vote a release alpha or beta, announce it, let others try it, and then upgrade the quality based on positive experience. An ASF release vote is not a political statement or a marketing vehicle. It's our best, ongoing assessment of whether the bits are ready to be deployed by the general public. -Ted. On 3/23/07, Philip Luppens <[EMAIL PROTECTED]> wrote:
Same here .. it would be easier if we could extend the period until after the weekend, making it easier for those not able to work on S2 during the day/week. Phil On 3/23/07, James Mitchell <[EMAIL PROTECTED]> wrote: > Unfortunately, I got pulled away on a critical issue and was not able > to run through this as fully as I would have liked. > > So +0 from me, unless I can find more time before the 72 hours runs out. > > > -- > James Mitchell > The Ruby Roundup > http://www.rubyroundup.com/ > > > On Mar 21, 2007, at 4:59 PM, Ted Husted wrote: > > > The Struts 2.0.7 test build is now available. > > > > Release notes: > > > > * http://struts.apache.org/2.x/docs/release-notes-207.html > > > > Distribution: > > > > * http://people.apache.org/builds/struts/2.0.7/ > > > > The Maven 2 staging repository is not yet available, but when it > > is, it will be in the usual location: > > > > * http://people.apache.org/builds/struts/2.0.7/m2-staging- > > repository/ > > > > Once you have had a chance to review the test build, please > > respond with a vote on its quality: > > > > [ ] 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. > > > > The vote will remain open for at least 72 hours, longer upon > > request. A vote can be amended at any time to upgrade or downgrade the > > quality of the release based on future experience. If an initial vote > > designates the build as "Beta", the release will be submitted for > > mirroring and announced to the user list. Once released as a public > > beta, subsequent quality votes on a build may be held on the user > > list. > > > > As always, the act of voting carries certain obligations. A > > binding vote not only states an opinion, but means that the voter is > > agreeing to help do the work > > > > -Ted.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
