Received: from maia.hub.org (maia-3.hub.org [200.46.204.243])
	by mail.postgresql.org (Postfix) with ESMTP id 08FB51337B69
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Wed,  9 Feb 2011 10:43:03 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia,
	port 10024) with ESMTP id 06692-02
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Wed,  9 Feb 2011 14:42:55 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 5DB11133616B
	for <pgsql-hackers@postgresql.org>;
	Wed,  9 Feb 2011 10:42:54 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p19EgkpT011465;
	Wed, 9 Feb 2011 09:42:46 -0500 (EST)
To: Andrew Dunstan <andrew@dunslane.net>
cc: Peter Eisentraut <peter_e@gmx.net>, Robert Haas <robertmhaas@gmail.com>,
	Simon Riggs <simon@2ndquadrant.com>, Aidan Van Dyk <aidan@highrise.ca>,
	Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>,
	pgsql-hackers@postgresql.org
Subject: Re: Sync Rep for 2011CF1 
In-reply-to: <4D529EE2.2010600@dunslane.net> 
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>
	<4D529EE2.2010600@dunslane.net>
Comments: In-reply-to Andrew Dunstan <andrew@dunslane.net>
	message dated "Wed, 09 Feb 2011 09:04:18 -0500"
Date: Wed, 09 Feb 2011 09:42:46 -0500
Message-ID: <11464.1297262566@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201102/726
X-Sequence-Number: 181515

Andrew Dunstan <andrew@dunslane.net> writes:
> On 02/09/2011 07:53 AM, Peter Eisentraut wrote:
>> 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.

> 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.

Yeah.  IIRC, in our first cycle using the CF process, we expected the
last CF to take longer than others.  I am not sure where the idea came
from that we'd be able to finish this one in a month.

I do accept the fact that we mustn't let it drag on indefinitely.
But two months instead of one isn't indefinite, and it seems more
realistic given the amount of work to be done.

			regards, tom lane