On 2/6/07, Craig McClanahan <[EMAIL PROTECTED]> wrote:
Isn't a feature of the current release practice that you could vote a
particular x.y.z release as "beta" now, but later hold another vote to
upgrade it to GA status later (i.e. without requiring another release)?
Don's success with it is great ... but that is only one data point. Having
10-50 people report back success would seem to mean it's time to go back and
give that release a better report card.
Craig
Yes, it is, and we've used the approach successfully with Struts 1.x.
It's nothing new. We've been using it for years, and so has HTTPD, and
Tomcat, and dozens of other projects.
Voting 2.0.5 beta now doesn't mean that it will stay at beta. It just
means that we will release it to the user list for wider testing. If
the user testing goes well, we can just promote 2.0.5 to GA, and
announce it again. Nothing changes except our opinion.
In the meantime, we can continue to make fixes and add features, and
roll 2.0.6 as soon as we like. Hopefully, 2.0.5 will go GA, and so
will 2.0.6. We had several GA releases in the 1.2.x series.
One thing I tried this time was to post the Quality vote the day the
test build went up. Next time, I'd like to try rolling on a Thursday,
so that we can hold the vote over the weekend, and maybe announce on
Monday.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
