| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Nearing beta? |
| Date: | 2013-04-11 15:42:27 |
| Message-ID: | 4260.1365694947@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> Tom Lane wrote:
>> The issue with event triggers causing catalog access during START
>> TRANSACTION is clearly a "must fix before beta" item. I'm afraid
>> that bug #8049 is going to require some nontrivial planner changes
>> (more about that in a bit), which means I'd like to get that into
>> the beta cycle too. What else are people aware of?
>>
>> Also, I'd say we need at least draft-quality release notes before
>> we can start beta, else beta testers won't know what to test.
> Maybe we should release an alpha with current git + draft release notes?
I would think that all three of the above-mentioned items could be
resolved in parallel, rather than doing one first. (I assume Bruce
hasn't got anything ready release-note-wise.)
Somebody previously suggested targeting the week of the 22nd for beta
(ie, wrap beta1 on Monday 4/22), and that still seems like it could
work, if there are no bigger problems than these.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-04-11 15:44:29 | Re: Nearing beta? |
| Previous Message | Alvaro Herrera | 2013-04-11 15:34:02 | Re: Nearing beta? |