pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Aidan Van Dyk <aidan@highrise.ca>
Cc: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Sync Rep for 2011CF1
Date: Wed, 09 Feb 2011 09:04:18 -0500
Message-ID: <4D529EE2.2010600@dunslane.net> (raw)
In-Reply-To: <1297256000.8685.217.camel@fsopti579.F-Secure.com>
References: <1295127631.3282.100.camel@ebony>
	<4D397FE4.2020709@enterprisedb.com>
	<1295616270.1803.10799.camel@ebony>
	<4D39A761.1020105@enterprisedb.com>
	<1295629194.1803.11957.camel@ebony>
	<AANLkTinFTZjur8gP+35eDKPGBjFRbdPmCTHT87e8r4mx@mail.gmail.com>
	<AANLkTikDK-1v6FfKGMA2j9VTPjnoC4ie_+c9dR2yHS3-@mail.gmail.com>
	<14761.1295633002@sss.pgh.pa.us>
	<AANLkTi=s4dHGt0my6QQ2oduhdyti8++bp4-_=Pxhzn7Z@mail.gmail.com>
	<AANLkTikG8WMhOocX9AYsRHYPc-PgxPaG6miFDD9QH3i1@mail.gmail.com>
	<1295703074.1803.19835.camel@ebony>
	<AANLkTimcwkbmL9qxiWRsCRA0CoFt5_ePE97CapF7xiw7@mail.gmail.com>
	<AANLkTimbcoPDUgZaX743ptg2e=99-zLgpVzjWWRvZoV8@mail.gmail.com>
	<1297096419.1770.5824.camel@ebony>
	<AANLkTikLyNAPoFmiQwT4pFj_sLtji1U=Bmc+dqKUVOnv@mail.gmail.com>
	<21347.1297100595@sss.pgh.pa.us>
	<AANLkTimX4DUMp5SmMGYMdmT_YwncLzJHpzJ+FbaDGAyW@mail.gmail.com>
	<1297256000.8685.217.camel@fsopti579.F-Secure.com>



On 02/09/2011 07:53 AM, Peter Eisentraut wrote:
> On mån, 2011-02-07 at 12:55 -0500, Robert Haas wrote:
>> On Mon, Feb 7, 2011 at 12:43 PM, Tom Lane<tgl@sss.pgh.pa.us>  wrote:
>>> Robert Haas<robertmhaas@gmail.com>  writes:
>>>> ... Well, the current CommitFest ends in one week, ...
>>> Really?  I thought the idea for the last CF of a development cycle was
>>> that it kept going till we'd dealt with everything.  Arbitrarily
>>> rejecting stuff we haven't dealt with doesn't seem fair.
>> Uh, we did that with 8.4 and it was a disaster.  The CommitFest lasted
>> *five months*. We've been doing schedule-based CommitFests ever since
>> and it's worked much better.
> The previous three commit fests contained about 50 patches each and
> lasted one month each.  The current commit fest contains about 100
> patches, so it shouldn't be surprising that it will take about 2 months
> to get through it.
>
> Moreover, under the current process, it is apparent that reviewing is
> the bottleneck.  More code gets written than gets reviewed.  By
> insisting on the current schedule, we would just push the growing review
> backlog ahead of ourselves.  The solution (at least short-term, while
> maintaining the process) has to be to increase the resources (in
> practice: time) dedicated to reviewing relative to coding.


Personally I think it's not unreasonable to extend the final commitfest 
of the release some. It doesn't need to be a huge amount longer, 
certainly not five months, but a couple of weeks to a month might be fair.

cheers

andrew



view thread (89+ messages)  latest in thread

Message-ID: <4D529EE2.2010600@dunslane.net>
Permalink:  ../4D529EE2.2010600@dunslane.net/
Also on:    postgresql.org/message-id/4D529EE2.2010600@dunslane.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: andrew@dunslane.net, peter_e@gmx.net, robertmhaas@gmail.com, tgl@sss.pgh.pa.us, simon@2ndquadrant.com, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com
  Subject: Re: Sync Rep for 2011CF1
  In-Reply-To: <4D529EE2.2010600@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox