| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: damage control mode |
| Date: | 2010-01-12 07:12:50 |
| Message-ID: | 162867791001112312l1ac9a21dsd8dd524bedc511ce@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-01-12 07:22:06 | Re: Streaming replication status |
| Previous Message | Andres Freund | 2010-01-12 05:40:02 | Re: Hot Standy introduced problem with query cancel behavior |