From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "Heikki Linnakangas" <heikki(at)enterprisedb(dot)com> |
Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 8.3 pending patch queue |
Date: | 2007-01-08 17:14:10 |
Message-ID: | 6858.65.211.31.251.1168276450.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
> I'm confused,
So I see.
> I thought the difference between the pgpatches queue and
> the pgpatches_hold queue is the release the patch is targeted for. If
> there's a third queue for patches that need review before being added to
> another queue, could we have that visible somewhere, so that we know
> what's in it?
>
>>
>> OK, naming suggestions?
>
> The "8.3 patch queue", and the "8.4 patch queue"?
>
The latter does not exist, AFAIK. Before feature freeze for cycle X, we
don't usually hold patches for release X+1, as I understand it.
In general, we should try to hold patches as little amount of time as
possible. That way they don't go stale as easily.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-08 17:16:55 | Re: [PATCHES] [Fwd: Index Advisor] |
Previous Message | Heikki Linnakangas | 2007-01-08 16:49:27 | Re: 8.3 pending patch queue |