Re: commitfest.postgresql.org is no longer fit for purpose
От | David G. Johnston |
---|---|
Тема | Re: commitfest.postgresql.org is no longer fit for purpose |
Дата | |
Msg-id | CAKFQuwZZSyV3GCc8F59+LceX=5QraM4oV9wp2Pt=UTK+81r=cg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: commitfest.postgresql.org is no longer fit for purpose (Joe Conway <mail@joeconway.com>) |
Ответы |
Re: commitfest.postgresql.org is no longer fit for purpose
|
Список | 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 по дате отправления: