Re: Commit fest 2019-09 - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Commit fest 2019-09
Date
Msg-id 20190930192415.GA31878@alvherre.pgsql
Whole thread Raw
In response to Re: Commit fest 2019-09  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Commit fest 2019-09
Re: Commit fest 2019-09
List pgsql-hackers
Hello,

After closing a few patches that have been dead for months, and moving
the rest to the next commitfest, here's the results:

      statusstring      │ week1 │ week2 │ week3 │ week4 │ final 
────────────────────────┼───────┼───────┼───────┼───────┼───────
 Needs review           │   165 │   138 │   116 │   118 │     0
 Waiting on Author      │    30 │    44 │    51 │    44 │     0
 Ready for Committer    │    11 │     5 │     8 │    11 │     0
 Returned with Feedback │     1 │     4 │     5 │     5 │    28
 Moved to next CF       │     2 │     4 │     4 │     4 │   191
 Committed              │    14 │    23 │    32 │    34 │    42
 Rejected               │     1 │     1 │     1 │     1 │     1
 Withdrawn              │     4 │     9 │    11 │    11 │    12

This means we got 28 patches committed during this month ... which is
a rather concerningly low figure.  I really hope we can do much better
in the upcoming three commitfests -- at least, we're not going to have
a stable release at the same time.

And with that, I've closed the commitfest.  I know there's still
technically a few hours left ... but if anyone wants to commit one more
patch, they can mark it committed in the next commitfest without
remorse.

Thanks everyone,

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Revert back to standard AC_STRUCT_TIMEZONE Autoconf macro
Next
From: Peter Geoghegan
Date:
Subject: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock(PG10.7)