Re: new commitfest transition guidance

Aleksander Alekseev <aleksander@timescale.com>

From: Aleksander Alekseev <aleksander@timescale.com>
To: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, Tom Lane <tgl@sss.pgh.pa.us>, Jacob Brazeal <jacob.brazeal@gmail.com>, Peter Geoghegan <pg@bowt.ie>, Tomas Vondra <tomas@vondra.me>, Jeff Davis <pgsql@j-davis.com>, Peter Eisentraut <peter@eisentraut.org>
Date: 2025-02-19T14:29:32Z
Lists: pgsql-hackers
Hi,

> I think this sounds much more reasonable than what's happening now.
> But I think we need to make the flow a bit more clear:
> 1. Add a "no interest" reason for closing.
> 2. Add a label[2]/column that specifies that an entry will be closed
> as "no interest" automatically at the end of this CF, e.g. a "pending
> no interest" label.
> 3. If at the end of a commitfest a patch has had 3 or more months
> without any emails, it automatically gets that "pending no interest"
> label.
> 4. Anyone subscribed to emails for this patch will get notified about
> that change.
> 5. If a patch is Ready for Committer and has a committer assigned,
> never add this label.
> 6. At the end of the commitfest, move all patches without that label.
> And close all patches with such a label.

Sounds perfect to me.

-- 
Best regards,
Aleksander Alekseev