I have done several passes to make sure that patch statuses are more
accurate. As explained in a nearby message, I have set several patches
back from "Ready to Committer" to "Needs review" if additional
discussion happened past the first status change. I have also in
several cases removed reviewers from a patch entry if they haven't been
active on the thread in several months. (Feel free to sign up again,
but don't "block" the patch.)
I was going to say, unfortunately that means that there is now even more
work to do, but in fact, it seems this has all kind of balanced out, and
I hope it's now more accurate for someone wanting to pick up some work:
Status summary: Needs review: 224. Waiting on Author: 24. Ready for
Committer: 31. Committed: 41. Returned with Feedback: 14. Withdrawn: 2.
Rejected: 2. Total: 338.
(And yes, the total number of patches has grown since the commitfest has
started!?!)
On 01.09.23 14:55, Peter Eisentraut wrote:
> Okay, here we go, starting with:
>
> Status summary: Needs review: 227. Waiting on Author: 37. Ready for
> Committer: 30. Committed: 40. Rejected: 1. Returned with Feedback: 1.
> Withdrawn: 1. Total: 337.
>
> (which is less than CF 2023-07)
>
> I have also already applied one round of the waiting-on-author-pruning
> described below (not included in the above figures).
>
>
> On 31.08.23 10:36, Peter Eisentraut wrote:
>> Commitfest 2023-09 (https://commitfest.postgresql.org/44/) starts in
>> less than 28 hours.
>>
>> If you have any patches you would like considered, be sure to add them
>> in good time.
>>
>> All patch authors, and especially experienced hackers, are requested
>> to make sure the patch status is up to date. If the patch is still
>> being worked on, it might not need to be in "Needs review".
>> Conversely, if you are hoping for a review but the status is "Waiting
>> on author", then it will likely be ignored by reviewers.
>>
>> There are a number of patches carried over from the PG16 development
>> cycle that have been in "Waiting on author" for several months. I
>> will aggressively prune those after the start of this commitfest if
>> there hasn't been any author activity by then.
>>
>>
>
>
>