Re: Patch queue concern

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Patch queue concern
Date: 2007-03-28 20:48:13
Message-ID: 87veglrt6a.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

> Simon Riggs wrote:
>
>> It's probably a good idea to have a queue of those too, to allow others
>> to finish them if the original author hasn't/can't/won't. I'm not sure
>> which ones you mean.
>
> At this point, with four days left before feature freeze, if the authors
> don't finish them, I doubt someone else is going to be able to do it.

This isn't the standard that we've used in the past. In the past patches that
are mostly done and need some extra work done to polish them off are
considered to have met the feature freeze.

In any case I think Simon and you have fallen into the trap of thinking of
development as a single-person project. Most developers here, especially
first-time contributors, don't just work in the dark on their own and turn up
with a finished patch. They have questions and need help in areas. If you
insist on a "finished" patch before you even consider reviewing their work
it's not going to work.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-03-28 20:51:46 Re: ECPG threads test
Previous Message Simon Riggs 2007-03-28 19:59:54 Re: Patch queue concern