From: | Jacob Champion <jchampion(at)timescale(dot)com> |
---|---|
To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, James Coleman <jtc331(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, Hou Zhijie <houzj(dot)fnst(at)fujitsu(dot)com>, Mats Kindahl <mats(at)timescale(dot)com>, "Drouvot, Bertrand" <bdrouvot(at)amazon(dot)com>, Denis Hirn <denis(dot)hirn(at)uni-tuebingen(dot)de>, Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, Daniil Zakhlystov <usernamedt(at)yandex-team(dot)ru> |
Subject: | Re: [Commitfest 2022-07] Patch Triage: Waiting on Author |
Date: | 2022-07-28 15:58:31 |
Message-ID: | CAAWbhmhnoJ584gXzji4q3WCo9P0vDu_-o6LPeMAGMyayJj6B5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 28, 2022 at 4:46 AM Andrey Borodin <x4mmm(at)yandex-team(dot)ru> wrote:
> Daniil is working on this, but currently he's on vacation.
> I think we should not mark patch as RwF and move it to next CF instead.
Is there a downside to marking it RwF, from your perspective? As
Robert pointed out upthread, it can be switched back at any time once
Daniil's ready.
Life happens; there isn't (or there shouldn't be) any shame in having
a patch returned temporarily. But it is important that patches which
aren't ready for review at the moment don't stick around for months.
They take up reviewer time and need to be triaged continually.
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2022-07-28 15:59:11 | Re: making relfilenodes 56 bits |
Previous Message | Jacob Champion | 2022-07-28 15:52:24 | Re: [Commitfest 2022-07] Patch Triage: Waiting on Author |