Re: Commitfest 2024-01 first week update

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest 2024-01 first week update
Date: 2024-01-09 22:18:36
Message-ID: CA+Tgmob_d7zzr4d2b=jQS3oLzsKkGMB8Rb=iMso_0DGe4bEWyw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I think we need to be more aggressive about marking things returned
with feedback when they don't get updated. If a patch is waiting for
reviews for a long time, well, that's one thing. Maybe we eventually
close it due to lack of interest in reviewing it, but that should be
done cautiously, as it will understandably piss people off. But I
regularly find patches in the CommitFest which have been waiting on
author for multiple commitfests and are just repeatedly moved forward.
That's crazy to me. It makes the CommitFest application fill up with
junk that obscures what actually needs to be dealt with.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2024-01-09 22:27:38 Re: Add BF member koel-like indentation checks to SanityCheck CI
Previous Message Jeremy Schneider 2024-01-09 22:17:44 Re: Built-in CTYPE provider