From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: We're getting close to the end of 2020-01 CF |
Date: | 2020-01-22 13:19:51 |
Message-ID: | 20200122131951.GA9025@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-Jan-22, Michael Paquier wrote:
> On Tue, Jan 21, 2020 at 05:20:17PM +0100, Tomas Vondra wrote:
> > Those are the patches that have been set as WoA before this CF, and have
> > not been updated since. It's quite possible the state is stale for some
> > of those patches, although I've tried to check if there were any
> > messages on the list.
>
> You need to be careful about bug fixes, as these are things that we
> don't want to lose track of.
Oh yeah, I forgot to mention the exception for bug fixes. I agree these
should almost never be RwF (or in any way closed other than Committed,
really, except in, err, exceptional cases).
> Another thing that I noticed in the past
> is that some patches are registered as bug fixes, but they actually
> implement a new feature. So there can be tricky cases.
Oh yeah, I think the CFM should exercise judgement and reclassify.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-01-22 13:32:49 | Re: Error message inconsistency |
Previous Message | Georgios Kokolatos | 2020-01-22 12:54:07 | Re: Duplicate Workers entries in some EXPLAIN plans |