Re: [Commitfest 2022-07] Patch Triage: Waiting on Author

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: James Coleman <jtc331(at)gmail(dot)com>
Cc: Jacob Champion <jchampion(at)timescale(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, 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-27 15:43:19
Message-ID: CA+TgmoYxn_W818g4xrR3nQNT7KFp5UCQKAb36iKhNBdK5zYpfQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jul 26, 2022 at 7:47 PM James Coleman <jtc331(at)gmail(dot)com> wrote:
> These are both mine, and I'd hoped to work on them this CF, but I've
> been sufficiently busy that that hasn't happened.
>
> I'd like to just move these to the next CF.

Well, if we mark them returned with feedback now, and you get time to
work on them, you can always change the status back to something else
at that point.

That has the advantage that, if you don't get time to work on them,
they're not cluttering up the next CF in the meantime.

We're not doing a great job kicking things out of the CF when they are
non-actionable, and thereby we are making life harder for ourselves
collectively.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Roberto C. Sánchez 2022-07-27 15:52:47 Re: Request for assistance to backport CVE-2022-1552 fixes to 9.6 and 9.4
Previous Message Andrew Dunstan 2022-07-27 15:21:15 Re: fairywren hung in pg_basebackup tests