Re: Commitfest problems - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Commitfest problems
Date
Msg-id 1485.1418317336@sss.pgh.pa.us
Whole thread Raw
In response to Re: Commitfest problems  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> On 12/11/14 1:35 AM, Bruce Momjian wrote:
>> While the commitfest process hasn't changed much and was very successful
>> in the first few years, a few things have changed externally:
>> 
>> 1  more new developers involved in contributing small patches
>> 2  more full-time developers creating big patches
>> 3  increased time demands on experienced Postgres developers

> The number of patches registered in the commit fests hasn't actually
> changed over the years.  It has always fluctuated between 50 and 100,
> depending on the point of the release cycle.  So I don't think (1) is
> necessarily the problem.

Interesting point, but of course not all patches are equal; perhaps
the problem is that we're seeing fewer of (1) and more of (2) in the
commitfest queue.  Is there any easy way to quantify the size/complexity
of the patches in past fests?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: double vacuum in initdb
Next
From: David G Johnston
Date:
Subject: Re: 9.5 release scheduling (was Re: logical column ordering)