On Mon, Oct 24, 2005 at 08:52:35AM -0400, Jeff Trawick wrote:
> 3 days is maybe enough time to catch a couple of build issues that we
> didn't see, but not anything else. I don't see the value in making a
> big deal about it to the general public if the thing is likely to be
> GA before there is time for more than a handful of people to give
> feedback. ("Why did I bother with the beta?")
I think it's prudent to release just one more beta release for public
review and see how it fares before we jump to GA.
So, I think we should do a 2.1.9 beta and then issue a complete feature
freeze on the branch (i.e. move to RTC on the branch; which we're doing
a piss-poor job of right now as everybody and their sister is merging
unreviewed feature changes into 2.2.x). Then, our next release can be a
GA target after we know that 2.1.9 had no problems and that branch is
essentially frozen so it can be stabilized.
I'd like to be more conservative about a 2.2.0 GA than we were with the
2.0 GAs which were extremely rushed. There's no reason for us to rush a
GA out right now: we've waited this long, duing another round of betas
will only help our eventual 2.2.0 GA quality. -- justin
