Re: [Commitfest 2022-07] Patch Triage: Waiting on Author

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [Commitfest 2022-07] Patch Triage: Waiting on Author
Дата
Msg-id CA+Tgmoab=R7uwPqqG6o9xHN0=vRrptTqQQe3tUBm=FML=y2KUQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [Commitfest 2022-07] Patch Triage: Waiting on Author  (Jacob Champion <jchampion@timescale.com>)
Ответы Re: [Commitfest 2022-07] Patch Triage: Waiting on Author  (Jacob Champion <jchampion@timescale.com>)
Список pgsql-hackers
On Mon, Aug 1, 2022 at 12:30 PM Jacob Champion <jchampion@timescale.com> wrote:
> Maybe this is something to look into once we've implemented some more of
> the low-hanging usability features that people have asked for. But if we
> started doing it now, I'd expect the CFM's job to simply change from
> moving patches ahead to pinging people who have patches left behind,
> asking them if they meant to move the patches forward. I'm not convinced
> it'd be all that useful.

We really need to move to a system where it's the patch author's job
to take some action if the patch is alive, rather than having the CM
(or any other human being) pinging to find out whether it's dead.
Having the default action for a patch be to carry it along to the next
CF whether or not there are any signs of life is unproductive.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



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

Предыдущее
От: Jacob Champion
Дата:
Сообщение: Re: [Commitfest 2022-07] Patch Triage: Waiting on Author
Следующее
От: Simon Riggs
Дата:
Сообщение: Smoothing the subtrans performance catastrophe