> The consensus view on this thread seems to be that we should have a > time-based code freeze, but not a time-based release. No one has > argued (and I sincerely hope no one will argue) that we should let the > last CommitFest drag on and on, as we did for 8.4. However, many > people are still eager to see us commit more large patches even though > they know that there are stop-ship issues in CVS HEAD as a result of > Hot Standby, and despite the fact that committing more large patches > will likely add more such issues. So, barring the possibility that we > somehow pull a collective rabbit out of our hat, we will NOT be ready > for beta on March 1. I have not yet given up hope on April 1, but I > wouldn't bet on it, either. >
+1 Pavel -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
