Commitfest 201709 is now closed

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Commitfest 201709 is now closed
Date: 2017-10-02 15:48:02
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

We have now entered October, which marks the end of Commitfest 201709. All
patches have now been dealt with and the commitfest is closed. Before starting
on moving, and closing, patches the stat for this commitfest were:

Needs review: 69.
Waiting on Author: 22.
Ready for Committer: 40.
Committed: 88.
Moved to next CF: 11.
Rejected: 8.
Returned with Feedback: 18.
Total: 256.

29 patches were in need of review but didn’t have a reviewer assigned (and no
review posted och -hackers), these have all been moved to the next CF. On top
of that, 40 patches were Ready for committer, and have been moved to the next
commitfest. The next commitfest is thus quite the smorgasbord for committers

A few patches had been "Waiting for author" during the entire commitfest
without seeing any updates, and were thus closed as “Returned with feddback”.
A few others patches were Returned with feedback too, due to either not moving
from Waiting for author, or due to review comments being made.

And last, but not least, a lot of patches were pushed to the next commitfest.
What I’ve tried to do is move patches such that every patch submitted has a
fair chance at a good review. Also, patches being actively discussed and
worked on were moved of course. With the volumes in mind, I’m absolutely
certain I’ve botched one or two up though. If you have a patch that was moved,
and you intend to rewrite enough of it to warrant a resubmission then please go
in and close your entry.

In summary, this commitfest saw a large number of patches, and while lots of
patches got reviewed and committed, there is a lot of improvement to be had
when it comes to closing them. We clearly need more bandwidth among reviewers
and committers to cope with the increasing size of the commitfests. There is a
clear risk that too much gets moved to the next commitfest making each new
commitfest progressively larger and harder to handle. I don’t have any good
answers, but we probably need to think of something going forward.

Thanks to everyone who participated, and to everyone who have responded to my
nagging via the CF app email function. This is clearly an awesome community.

cheers ./daniel


Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2017-10-02 15:49:48 Issues with logical replication
Previous Message Konstantin Knizhnik 2017-10-02 15:47:48 Issues with logical replication