Message-ID: <ccc8daae-374a-4162-a5a3-b39498af01d7@comcast.net>
Date: Thu, 16 May 2024 17:00:57 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
To: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
References: <CA+TgmobnTcNq1xQE_+jxBEtj+AjKg0r_p5YNFHDE+EDnpcpFxA@mail.gmail.com>
 <50435844-54E0-4100-AE23-C72FF4134F92@yesql.se>
 <2145897.1715888840@sss.pgh.pa.us>
 <ee8be88a-8d6e-4a2f-8de2-7a068012c698@joeconway.com>
Content-Language: en-US
From: Jesper Pedersen <jesper.pedersen@comcast.net>
In-Reply-To: <ee8be88a-8d6e-4a2f-8de2-7a068012c698@joeconway.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/ccc8daae-374a-4162-a5a3-b39498af01d7%40comcast.net>
Precedence: bulk

Hi,

On 5/16/24 4:31 PM, Joe Conway wrote:
>> Yeah.  I think that Robert put his finger on a big part of the
>> problem, which is that punting a patch to the next CF is a lot
>> easier than rejecting it, particularly for less-senior CFMs
>> who may not feel they have the authority to say no (or at
>> least doubt that the patch author would accept it).
> 
> Maybe we should just make it a policy that *nothing* gets moved forward 
> from commitfest-to-commitfest and therefore the author needs to care 
> enough to register for the next one?
>

Or at least nothing get moved forward from March.

Spending time on a patch during a major version doesn't mean that you 
have time to do the same for the next major version.

That way July could start "clean" with patches people are interested in 
and willing to maintain during the next year.

Also, it is a bit confusing that f.ex.

  https://commitfest.postgresql.org/48/

already shows 40 patches as Committed...

So, having some sort of "End of Development" state in general would be good.

Best regards,
  Jesper