On 2/21/07, Don Brown <[EMAIL PROTECTED]> wrote:
I completely agree. It is unrealistic for an active project that uses this particular release process to find/fix zero bugs and make zero improvements from the time the test build is created to when it is voted upon.
We've started to call the votes as soon as the test build is available, so there isn't any lag time. Hopefully, people here have already been working with the HEAD, so it should be a final shakedown.
The metric should be, even knowing what you do, if you tested the release and find it meets your standard of quality. Since this particular issue was present in WW for many GA releases, I don't think it should affect the quality vote for this release, but that doesn't mean we shouldn't roll 2.0.7 quickly and also possibly make it GA.
Just to touch all the bases, releases are a majority vote, and all we need is three binding +1s and more +1s and -1s. So, even if someone were to apply a tougher metric, a binding beta vote would not stop a GA, so long as we had more binding GA votes than beta or test-build votes. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
