Re: Commitfest problems - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Commitfest problems
Date
Msg-id 20141211193625.GD19832@momjian.us
Whole thread Raw
In response to Re: Commitfest problems  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Thu, Dec 11, 2014 at 11:49:43AM -0500, Peter Eisentraut wrote:
> 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.

Yes, I was hoping someone would produce some numbers --- thanks.  I
think the big question is whether the level of complexity of the patches
has increased, or whether it is just the amount of experienced developer
time (3) that has decreased, or something else.  Or maybe things have
not materially changed at all over the years.

I am following this thought process:
1.  Do we have a problem?2.  What is the cause of the problem?3.  How do we fix the problem?

I think to get a useful outcome we have to process things in that order.
So, is #1 true, and if so, what is the answer to #2?

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: PATCH: hashjoin - gracefully increasing NTUP_PER_BUCKET instead of batching
Next
From: Tom Lane
Date:
Subject: Re: Final Patch for GROUPING SETS