pg.ddx.io pgsql-hackers@postgresql.org mailing list archive
help / color / mirror / Atom feedCommitfest PG20-2 is now closed
5+ messages / 4 participants
[nested] [flat]
* Commitfest PG20-2 is now closed
@ 2026-10-01 02:56 shihao zhong <zhong950419@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: shihao zhong @ 2026-10-01 02:56 UTC (permalink / raw)
To: pgsql-hackers <pgsql-hackers@lists.postgresql.org>; +Cc: Andrey Borodin <x4mmm@yandex-team.ru>
Hi,
The September CommitFest, PG20-2, is now closed. Thanks to everyone who
reviewed, committed, or kept a patch rebased.
It had 539 entries and 116 were committed. Both are the highest for a
September CommitFest since 2015. Last September had 307 entries and 69
commits. 28 were withdrawn, 4 returned with feedback, 1 rejected, and 55
moved to another CommitFest before the close.
Andrey and I changed the status of 54 entries whose CF status did not
match the thread, most often to Waiting on Author or Ready for
Committer. We also merged three pairs of duplicate entries. If we got
one wrong, tell us and we will fix it.
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. If one is yours and still active, please move it from your
dashboard.
https://commitfest.postgresql.org/?author=-3
31 of those are Ready for Committer, most with no email since August.
Committers looking for something to pick up could start there.
Thanks to Andrey for sharing the role and for the guidance.
PG20-3 starts on November 1 and does not have a manager yet. I will not
take it myself, but I am happy to help whoever volunteers.
Regards,
Shihao
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Commitfest PG20-2 is now closed
@ 2026-10-01 08:27 Álvaro Herrera <alvherre@kurilemu.de>
parent: shihao zhong <zhong950419@gmail.com>
0 siblings, 1 reply; 5+ messages in thread
From: Álvaro Herrera @ 2026-10-01 08:27 UTC (permalink / raw)
To: shihao zhong <zhong950419@gmail.com>; +Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>; Andrey Borodin <x4mmm@yandex-team.ru>
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=...
https://commitfest.postgresql.org/59/?text=&status=-1&targetversion=-1&tag=1&author=...
https://commitfest.postgresql.org/61/?text=&status=-1&targetversion=-1&tag=1&author=...
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)
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Commitfest PG20-2 is now closed
@ 2026-10-01 15:00 Jacob Champion <jacob.champion@enterprisedb.com>
parent: Álvaro Herrera <alvherre@kurilemu.de>
0 siblings, 1 reply; 5+ messages in thread
From: Jacob Champion @ 2026-10-01 15:00 UTC (permalink / raw)
To: Álvaro Herrera <alvherre@kurilemu.de>; +Cc: shihao zhong <zhong950419@gmail.com>; pgsql-hackers <pgsql-hackers@lists.postgresql.org>; Andrey Borodin <x4mmm@yandex-team.ru>
On Thu, Oct 1, 2026 at 1:28 AM Álvaro Herrera <alvherre@kurilemu.de> wrote:
> 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.
+1
--Jacob
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Commitfest PG20-2 is now closed
@ 2026-10-01 19:48 Jelte Fennema-Nio <postgres@jeltef.nl>
parent: Jacob Champion <jacob.champion@enterprisedb.com>
0 siblings, 1 reply; 5+ messages in thread
From: Jelte Fennema-Nio @ 2026-10-01 19:48 UTC (permalink / raw)
To: Jacob Champion <jacob.champion@enterprisedb.com>; +Cc: Álvaro Herrera <alvherre@kurilemu.de>; shihao zhong <zhong950419@gmail.com>; pgsql-hackers <pgsql-hackers@lists.postgresql.org>; Andrey Borodin <x4mmm@yandex-team.ru>
On Thu, 1 Oct 2026 at 11:01, Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
>
> On Thu, Oct 1, 2026 at 1:28 AM Álvaro Herrera <alvherre@kurilemu.de> wrote:
> > 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.
>
> +1
Yeah agreed, should be easy to fix
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: Commitfest PG20-2 is now closed
@ 2026-10-02 04:09 shihao zhong <zhong950419@gmail.com>
parent: Jelte Fennema-Nio <postgres@jeltef.nl>
0 siblings, 0 replies; 5+ messages in thread
From: shihao zhong @ 2026-10-02 04:09 UTC (permalink / raw)
To: Jelte Fennema-Nio <postgres@jeltef.nl>; +Cc: Jacob Champion <jacob.champion@enterprisedb.com>; Álvaro Herrera <alvherre@kurilemu.de>; pgsql-hackers <pgsql-hackers@lists.postgresql.org>; Andrey Borodin <x4mmm@yandex-team.ru>
Hi Alvaro,
> IMO all patches tagged "Bugfix" should be moved forward, regardless of
> thread noise level or whether CI is clean or not.
Agreed. I went through the open Bugfix entries in your three lists.
58 are now in PG20-3, with the tag kept.
7 lost the tag and stayed where they were. Their own threads call them
improvements or hardening, for example psql tab completion and an
added Assert.
5 are closed. 3 were already committed. The other two:
https://commitfest.postgresql.org/patch/5736/
Returned with Feedback. The race only shows up after a code change,
and the thread has been quiet since May 2025.
https://commitfest.postgresql.org/patch/7070/
Rejected. Daniel did not want the change, and the other fixes from
that thread are committed.
If I got one wrong, tell me or just change it back.
For the commitfest app, I opened two PRs.
https://github.com/postgres/pgcommitfest/pull/120
Entries tagged Bugfix are always moved when a CommitFest closes.
https://github.com/postgres/pgcommitfest/pull/121
The "Attach thread" search also finds pgsql-bugs threads, so a fix for
a bug report is easier to register.
Thanks,
Shihao
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2026-10-02 04:09 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-10-01 02:56 Commitfest PG20-2 is now closed shihao zhong <zhong950419@gmail.com>
2026-10-01 08:27 ` Álvaro Herrera <alvherre@kurilemu.de>
2026-10-01 15:00 ` Jacob Champion <jacob.champion@enterprisedb.com>
2026-10-01 19:48 ` Jelte Fennema-Nio <postgres@jeltef.nl>
2026-10-02 04:09 ` shihao zhong <zhong950419@gmail.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox