Re: 2022-01 Commitfest

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: 2022-01 Commitfest
Date: 2022-02-02 18:00:18
Message-ID: 15915.1643824818@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> writes:
> On Thu, Feb 03, 2022 at 01:28:53AM +0800, Julien Rouhaud wrote:
>> If we close all patches that had a review just because they weren't perfect in
>> their initial submission, we're just going to force everyone to re-register
>> their patch for every single commit fest. I don't see that doing anything
>> apart from making sure that everyone stops contributing.

> I had the same problem last time, "Returned with feedback" didn't feel
> fine in some cases.

Agreed, we're not here to cause make-work for submitters. RWF is
appropriate if the patch has been in Waiting On Author for awhile
and doesn't seem to be going anywhere, but otherwise we should
just punt it to the next CF.

Anyway, thanks to Julien for doing this mostly-thankless task
this time!

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2022-02-02 18:10:39 Re: 2022-01 Commitfest
Previous Message Julien Rouhaud 2022-02-02 17:56:56 Re: 2022-01 Commitfest