Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 7AC589FB530; Mon, 30 Apr 2007 08:27:15 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 19782-05; Mon, 30 Apr 2007 08:27:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 3D2EB9FB504; Mon, 30 Apr 2007 08:27:12 -0300 (ADT) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id l3UBRAS19593; Mon, 30 Apr 2007 07:27:10 -0400 (EDT) From: Bruce Momjian Message-Id: <200704301127.l3UBRAS19593@momjian.us> Subject: Re: Feature freeze progress report In-Reply-To: <4634FCFF.5040806@postgresql.org> To: Dave Page Date: Mon, 30 Apr 2007 07:27:10 -0400 (EDT) CC: Stefan Kaltenbrunner , Heikki Linnakangas , Simon Riggs , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL123] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200704/1236 X-Sequence-Number: 102569 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'm not advocating committing patches that might destabilize the code, > I'm suggesting making it easier for individual committers to make use of > the knowledge and experience of everyone else in the community, whilst > at the same time reducing the reliance on their own experience. Even now > we occasionally see patches getting committed that (for example) Tom has > rejected months earlier. At the very least a tracker should help prevent > that happening, at best it will help committers work faster and more > effectively because they have all the relevant discussion in front of them. This gets back to the same issue as a bug trackers --- the information has to be managed or it just becomes a dumping ground, and who is going to do that if the community can't even comment on some patches. -- Bruce Momjian http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +