Re: Commitfest 2022-03 One Week in. 3 Commits 213 Patches Remaining

Поиск
Список
Период
Сортировка
От Greg Stark
Тема Re: Commitfest 2022-03 One Week in. 3 Commits 213 Patches Remaining
Дата
Msg-id CAM-w4HPYbUkpBq0kjCA3x5hpyJXFF_Ep_EJ_n4OE82x4JBGxpA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Commitfest 2022-03 One Week in. 3 Commits 213 Patches Remaining  (David Steele <david@pgmasters.net>)
Ответы Re: Commitfest 2022-03 One Week in. 3 Commits 213 Patches Remaining  (Greg Stark <stark@mit.edu>)
Список pgsql-hackers
On Wed, 9 Mar 2022 at 15:44, David Steele <david@pgmasters.net> wrote:
>
> On 3/9/22 13:38, Greg Stark wrote:
> Should I do a round-robin style assignment for any of these?
>
> I don't think this is a good idea. Committers pick the patches they are
> going to commit.
>
> What prefer to do is bump any committers that have been involved in a
> patch thread to see if they are willing to commit it.

Well yes, I suppose that's probably what I had in mind despite calling it that.

But I've been skimming the set of "Ready for Committer" patches and
I'm a bit down on them. Many of them seem to mostly have gotten
feedback from committers already and the type of feedback that leads
me to think it's ready for commit.

I suppose people mark patches "Ready for Committer" when the level of
feedback they require is more in depth or more design feedback that
they think requires a committer even if it's not ready for commit.

So I'm going to go through the patches and ask the committers who have
already commented if they think the patch is on track to be committed
this release or should be pushed to the next commitfest.

-- 
greg



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: role self-revocation
Следующее
От: Greg Stark
Дата:
Сообщение: Re: Commitfest 2022-03 One Week in. 3 Commits 213 Patches Remaining