Hi Shihao, thanks for spending time with the commitfest. I think we've
now reached a point where to amount of effort spent managing it is no
longer visible.
On 2026-Sep-30, shihao zhong wrote:
> At close the app moved 140 active entries to PG20-3. 195 stayed behind
> because the thread was quiet in September or CI had failed for over
> three weeks.
Since the redesign of the commitfest app and the abandonment of the
commitfest manager post, there's something happening that worries me:
old bug fixes become invisible in older commitfests because they're no
longer being carried forward. IMO the automated rules about what is
moved forward don't match perfectly well what we used to do when the
process was manual, or at least what *I* used to do. There's a few
bugfixes in all these CFs that, from what I can tell, are not yet
committed:
https://commitfest.postgresql.org/58/?text=&status=-1&targetversion=-1&tag=1&author=-1&reviewer=-1&sortkey=
https://commitfest.postgresql.org/59/?text=&status=-1&targetversion=-1&tag=1&author=-1&reviewer=-1&sortkey=
https://commitfest.postgresql.org/61/?text=&status=-1&targetversion=-1&tag=1&author=-1&reviewer=-1&sortkey=
IMO all patches tagged "Bugfix" should be moved forward, regardless of
thread noise level or whether CI is clean or not. At the same time,
it's probably appropriate for the CFM to remove the Bugfix tag from
entries that aren't backpatchable bugfixes, and it's also OK to close
entries as "rejected" or "withdrawn" as appropriate.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Las navajas y los monos deben estar siempre distantes" (Germán Poo)
