From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Alvaro Herrera <alvherre(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 14:26:18 |
Message-ID: | 20200122142618.iu4ejuaoyhbu2lpy@development |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 22, 2020 at 02:09:39PM +0900, Michael Paquier wrote:
>On Tue, Jan 21, 2020 at 05:20:17PM +0100, Tomas Vondra wrote:
>> Yeah, you're right returning them with feedback seems more appropriate,
>> given the long inactivity. Plus, the CF app apparently does not allow
>> moving WoA patches to the next CF anyway.
>
>FWIW, I tend to take a base of two weeks as a sensible period of
>time as that's half the CF period when I do the classification job.
>
Yeah. I've only nagged about patches that have been set to WoA before
the CF began, so far.
>> 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. 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.
>--
Makes sense.
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-01-22 15:05:39 | Re: Do we need to handle orphaned prepared transactions in the server? |
Previous Message | Alvaro Herrera | 2020-01-22 13:32:49 | Re: Error message inconsistency |