Commitfest 2023-09 has finished

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Commitfest 2023-09 has finished
Date: 2023-10-02 18:27:00
Message-ID: f3e6758d-58da-a195-de8a-ccf547ac0620@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

As September has ended, I have closed commitfest 2023-09. The status
before I started moving patches over was

Status summary: Needs review: 189. Waiting on Author: 30. Ready for
Committer: 28. Committed: 68. Moved to next CF: 1. Returned with
Feedback: 16. Rejected: 1. Withdrawn: 5. Total: 338.

The final status is now

Status summary: Committed: 68. Moved to next CF: 248. Withdrawn: 5.
Rejected: 1. Returned with Feedback: 16. Total: 338.

The "Committed" number is lower than in the preceding commitfests, but
it is actually higher than in the September commitfests of preceding years.

I did some more adjustments of status and removal of stale reviewer
entries. But overall, everything looked pretty accurate and up to date.

In the November commitfest right now, there are more than 50 patches
that are 2 or 3 CFs old (meaning they arrived after PG16 feature freeze)
and that have no reviewers. Plus at least 30 patches without reviewers
that are completely new in the November CF. Also, it looks like a lot
of these are in the Performance category, which is typically harder to
review and get agreement on. So, while we do have some really old
patches that, well, are hard to get sorted out, there is a lot of new
work coming in that really just needs plain reviewer attention.

Browse pgsql-hackers by date

  From Date Subject
Next Message PG Doc comments form 2023-10-02 18:42:14 unnest multirange, returned order
Previous Message Robert Haas 2023-10-02 18:10:46 Re: On login trigger: take three