From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules) |
Date: | 2009-01-25 19:54:52 |
Message-ID: | 3073cc9b0901251154w1a8d4c1br5cfacde62cd3ffa7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jan 25, 2009 at 12:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> and I'm beginning to think that we need to invoke that provision.
> Particularly with regard to hot standby, which by any sane reading was
> not close to being committable on 1 November (a fortiori from the fact
> that it's *still* not committable despite large amounts of later work).
maybe what we need is to put a policy for large patches... something
like: if you submit a large patch that introduce fairly complex new
features very late in the release cycle (maybe at the last commit fest
or previous to that one) then there are no promises about committers
to review them... maybe that will enforce authors to send patches more
often and more early...
and of course, the rest of us that make some kind of review (call it:
testing or code review) should start making those reviews on large
patches (just like someone suggests)
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | Emmanuel Cecchet | 2009-01-25 20:11:15 | Re: Table Partitioning Feature |
Previous Message | Tom Lane | 2009-01-25 18:36:35 | Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle |