From: Peter Eisentraut <peter_e@gmx.net>
To: pgsql-hackers@postgresql.org
Subject: Re: Getting a move on for 8.2 beta
Date: Sat, 2 Sep 2006 02:09:35 +0200
User-Agent: KMail/1.9.3
Cc: Tom Lane <tgl@sss.pgh.pa.us>, josh@agliodbs.com,
	Bruce Momjian <bruce@momjian.us>
References: <200609012225.k81MPwJ02170@momjian.us>
	<200609011639.42280.josh@agliodbs.com>
	<26043.1157154656@sss.pgh.pa.us>
In-Reply-To: <26043.1157154656@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200609020209.36483.peter_e@gmx.net>

Tom Lane wrote:
> Well, no, it's not.  We have told people till we're blue in the face
> "post early, post often".  Now I will plead guilty to not always
> having spent as much time giving feedback on draft patches as I
> should've, but the process is pretty clear.  As I see it the main
> problem is people undertaking patches off in corners somewhere rather
> than discussing their work on the mailing lists while they do it.

Again, process support.  If all we can offer people is to post 
multi-megabyte patches to the mailing list every month, that totally 
doesn't help.  We'd need ways to track the progress on these things: 
what was the specification for that patch, where was the discussion on 
it, what has changed in the patch since the last time, since the time 
before last time, what is left to be done, who has worked on it, etc.  
Figuring out the answer to those questions from a mailing list archive 
is tedious to the point that no one wants to do it.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/