Re: new commitfest transition guidance

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Aleksander Alekseev <aleksander(at)timescale(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Tomas Vondra <tomas(at)vondra(dot)me>, Jeff Davis <pgsql(at)j-davis(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: new commitfest transition guidance
Date: 2025-02-19 16:24:24
Message-ID: 99545D06-F275-4C16-867D-1D338F7A96E3@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 19 Feb 2025, at 16:24, Aleksander Alekseev <aleksander(at)timescale(dot)com> wrote:
>
> Hi,
>
>> How about having the cfbot send out some nagmail to patch authors,
>> saying "please move your patch forward, or close it if no longer
>> interested"? If nothing happens after a few rounds of that,
>> an auto-close could be justified.
>
> Well, it is a possibility of course. If I read the current status of
> January CF correctly this means sending 80 emails to an unknown number
> of pgsql-hackers@ subscribers though.

There is functionality in the CF app to send an email to authors with a patch
still in the previous commitfest, it would be quite trivial to alert everyone.

We should of course also add some form of messaging in the app itself to make
it known that patches need to be moved etc.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2025-02-19 16:27:13 Re: new commitfest transition guidance
Previous Message Alvaro Herrera 2025-02-19 15:46:55 Re: Support for NO INHERIT to INHERIT state change with named NOT NULL constraints