Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close
Date
Msg-id 40b0fb79-d5e1-4134-b963-80eafad0c4bf@eisentraut.org
Whole thread Raw
Responses Re: Huge commitfest app update upcoming: Tags, Draft CF, Help page, and automated commitfest creat/open/close
List 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.




pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: minimum Meson version
Next
From: Fabrice Chapuis
Date:
Subject: Prevent numeric literals from having non-numeric trailing characters (Peter Eisentraut)