Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Jelte Fennema-Nio <postgres@jeltef.nl>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>,
Jacob Champion <jacob.champion@enterprisedb.com>,
Florents Tselai <florents.tselai@gmail.com>
Date: 2025-06-20T13:21:40Z
Lists: pgsql-hackers
On 16.06.25 14:47, Jelte Fennema-Nio wrote: > # Draft CF > > There's now an additional Draft CF. People can move patches there as a > way of not forgetting about them. CFBot will rerun these patches less > frequently (exact behaviour TBD). Draft CFs are never "In Progress" > and are open until the final CF of the release cycle becomes "In > Progress". So PG19-Drafts will close on February 28th 2026, and at the > same moment PG20-Drafts will be opened. Can we clarify the expectations around this? In some early discussions, I had heard this being talked about as a "parking lot". You can put patches there so that they get CI runs, but no one else is really expected to pay attention to them. Makes sense. But many patches that are routinely submitted to normal commit fests are really drafts, in that they are in an early phase of development but still need feedback. I sense there could be some confusion whether such draft patches should go into the regular commit fest or the draft commit fest, and then also when they should move between them.