Commitfest 2024-01 fourth week update

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Commitfest 2024-01 fourth week update
Date: 2024-01-29 03:37:50
Message-ID: CALDaNm314W4Ahd-zRMOpAL0Fqg2rWe2K-tLVdzvntXuTQePOGg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Here's a quick status report after the fourth week:
Status summary:
status | w1 | w2 | w3 | w4
-----------------------------------+-----------+--------+--------+----------
Needs review: | 238 | 213 | 181 | 147
Waiting on Author: | 44 | 46 | 52 | 65
Ready for Committer: | 27 | 27 | 26 | 24
Committed: | 36 | 46 | 57 | 70
Moved to next CF | 1 | 3 | 4 | 4
Withdrawn: | 2 | 4 | 12 | 14
Returned with Feedback: | 3 | 12 | 18 | 26
Rejected: | 1 | 1 | 2 | 2
Total: | 352 | 352 | 352 | 352

If you have submitted a patch and it's in "Waiting for author" state,
please aim to get it to "Needs review" state soon if you can, as
that's where people are most likely to be looking for things to
review.

I have pinged all the threads that are in "Needs review" state and
don't apply, compile warning-free, or pass check-world. I'll do some
more of that sort of thing.

I have sent out mails for which there has been no activity for a long
time, please respond to the mails if you are planning to continue to
work on it or if you are planning to work on it in the next
commitfest, please move it to the next commitfest. If there is no
response I'm planning to return these patches and it can be added
again when it will be worked upon actively.

Regards,
Vignesh

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2024-01-29 03:40:00 Re: Wrong rows estimations with joins of CTEs slows queries by more than factor 500
Previous Message Junwang Zhao 2024-01-29 03:37:07 Re: Make COPY format extendable: Extract COPY TO format implementations