Re: commitfest.postgresql.org is no longer fit for purpose - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: commitfest.postgresql.org is no longer fit for purpose
Date
Msg-id CAKFQuwZZSyV3GCc8F59+LceX=5QraM4oV9wp2Pt=UTK+81r=cg@mail.gmail.com
Whole thread Raw
In response to Re: commitfest.postgresql.org is no longer fit for purpose  (Joe Conway <mail@joeconway.com>)
Responses Re: commitfest.postgresql.org is no longer fit for purpose
List 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.

pgsql-hackers by date:

Previous
From: "Andrey M. Borodin"
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Next
From: Alexander Lakhin
Date:
Subject: Re: Streaming read-ready sequential scan code