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

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Peter Eisentraut <peter_e@gmx.net>
Cc: Robert Haas <robertmhaas@gmail.com>
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:42:46 -0500
Message-ID: <11464.1297262566@sss.pgh.pa.us> (raw)
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>

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



view thread (89+ messages)  latest in thread

Message-ID: <11464.1297262566@sss.pgh.pa.us>
Permalink:  ../11464.1297262566@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/11464.1297262566@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, andrew@dunslane.net, peter_e@gmx.net, robertmhaas@gmail.com, simon@2ndquadrant.com, aidan@highrise.ca, heikki.linnakangas@enterprisedb.com
  Subject: Re: Sync Rep for 2011CF1
  In-Reply-To: <11464.1297262566@sss.pgh.pa.us>

* 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