Date: Mon, 30 Apr 2007 15:17:36 +0200
From: Magnus Hagander <magnus@hagander.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Dave Page <dpage@postgresql.org>,
	Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>,
	Heikki Linnakangas <heikki@enterprisedb.com>,
	Simon Riggs <simon@2ndquadrant.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Feature freeze progress report
Message-ID: <20070430131736.GA13927@svr2.hagander.net>
References: <4634FCFF.5040806@postgresql.org>
	<200704301127.l3UBRAS19593@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200704301127.l3UBRAS19593@momjian.us>
User-Agent: Mutt/1.5.11

On Mon, Apr 30, 2007 at 07:27:10AM -0400, Bruce Momjian wrote:
> Dave Page wrote:
> > I'm not specifically talking about complex patches (nor am I talking at
> > all about bug tracking) - there are a variety of patches in the queue,
> > of varying complexity. Some have been there for months, and worse, some
> > of them recieved little or no feedback when submitted leaving the
> > authors completely in the dark about whether their work will be
> > included, whether further changes are required, or whether they should
> > continue with additional enhancements.
> 
> Agreed.  Remember that patches queue is just patches that no one has
> dealt with.  It was never designed to be a community thing, but Tom and
> others do pull from it as necessary.  If the community dealt with all
> patches, I wouldn't have to add anything to the queue.

I think that summarises the problem with it fairly well. It was never
designde to be a community thing. But we need a community thing now (we
didn't at the time, probably). Oh, and you are of course no less community
than anybody else ;-)

//Magnus