Re: 2017-03 Commitfest In Progress

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: David Steele <david(at)pgmasters(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 2017-03 Commitfest In Progress
Date: 2017-03-02 01:28:07
Message-ID: 1512.1488418087@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> On Thu, Mar 2, 2017 at 4:42 AM, David Steele <david(at)pgmasters(dot)net> wrote:
>> The 2017-03 commitfest is now in progress. Here's the breakdown:
>>
>> Needs review: 128
>> Waiting on Author: 26
>> Ready for Committer: 26
>> Total: 180

> Not quite a record haul but close.

Indeed. As usual, a depressingly large number of patches appeared out of
the woodwork in the last few days before the deadline, and more than a
couple of those seem to be clear violations of our rule about "no major
new features should first appear during the last commitfest".

I think we should have a discussion about which patches need to be booted
to the next CF (ie, first of the v11 cycle) without further attention now.
ISTM it would be quite unfair if patches that have been in the queue for
much longer fail to get into v10 because johnny-come-lately patches
consumed reviewer and committer bandwidth.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-03-02 01:39:07 Re: mat views stats
Previous Message Jim Nasby 2017-03-02 01:25:23 Re: REINDEX CONCURRENTLY 2.0