Re: Commitfest 2024-01 first week update - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Commitfest 2024-01 first week update
Date
Msg-id CA+Tgmob_d7zzr4d2b=jQS3oLzsKkGMB8Rb=iMso_0DGe4bEWyw@mail.gmail.com
Whole thread Raw
In response to Commitfest 2024-01 first week update  (vignesh C <vignesh21@gmail.com>)
Responses Re: Commitfest 2024-01 first week update
Re: Commitfest 2024-01 first week update
List 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



pgsql-hackers by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: Built-in CTYPE provider
Next
From: Tom Lane
Date:
Subject: Re: Add BF member koel-like indentation checks to SanityCheck CI