Re: commitfest.postgresql.org is no longer fit for purpose

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>

To: Joe Conway <mail@joeconway.com>

Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Peter Eisentraut <peter@eisentraut.org>, Melanie Plageman <melanieplageman@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>

Date: 2024-05-17T12:51:22Z

Lists: pgsql-hackers

On Friday, May 17, 2024, Joe Conway <mail@joeconway.com> wrote:

>
> I wrote:
>
>> Namely, the week before commitfest I don't actually know if I will have
>> the time during that month, but I will make sure my patch is in the
>> commitfest just in case I get a few clear days to work on it. Because if it
>> isn't there, I can't take advantage of those "found" hours.
>>
>
> A solution to both of these issues (yours and mine) would be to allow
> things to be added *during* the CF month. What is the point of having a
> "freeze" before every CF anyway? Especially if they start out clean. If
> something is ready for review on day 8 of the CF, why not let it be added
> for review?
>

In conjunction with WIP removing this limitation on the bimonthlies makes
sense to me.

David J.