| From: | Jacob Brazeal <jacob(dot)brazeal(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new commitfest transition guidance |
| Date: | 2025-02-06 17:57:20 |
| Message-ID: | CA+COZaAZO+7U9o0pPJ6J6GrHpjUc5Ve97Damg1X3yLfCckW6oQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>
> That's not entirely true. CFBot never runs on patches that are only in
> closed commitfests.
>
> Ofcourse the CFBot could be changed to
> behave differently, but then the question becomes how should it behave
> then? When do we want to stop running CFBot on patches?
>
> Related: What do we do in general with patches that have been moved?
> And when do we do that?
>
It seems clear that if new patches are pushed to a message thread that was
registered with commitfest at some point, we'd like CFBot to run on them.
What if we automatically move any patches to the current commitfest if new
patch attachments are sent to the corresponding message thread? Heck,
perhaps if there are any new messages *at all* in the message thread, and
the commitfest entry has not been closed already, we should move it to the
current commitfest. We could even have commitfest respond to the message
thread to inform when automated actions of this nature have been taken.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2025-02-06 18:06:01 | Re: Confine vacuum skip logic to lazy_scan_skip |
| Previous Message | Jeff Davis | 2025-02-06 17:52:03 | Re: new commitfest transition guidance |