Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CDDA02E0054 for ; Mon, 24 Mar 2008 16:20:46 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 71324-06 for ; Mon, 24 Mar 2008 16:20:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id C23192E0056 for ; Mon, 24 Mar 2008 16:20:35 -0300 (ADT) Received: from perhan.alvh.no-ip.org (200-126-66-43.bk5-dsl.surnet.cl [200.126.66.43]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id m2OJKmWw020124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Mar 2008 12:20:51 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 6305847BFE; Mon, 24 Mar 2008 16:20:14 -0300 (CLST) Date: Mon, 24 Mar 2008 16:20:14 -0300 From: Alvaro Herrera To: Bruce Momjian Cc: Stefan Kaltenbrunner , Andrew Sullivan , PostgreSQL-development Subject: Re: [pgsql-www] New email list for emergency communications Message-ID: <20080324192014.GI5484@alvh.no-ip.org> References: <47E7F825.9020902@kaltenbrunner.cc> <200803241909.m2OJ9RX08326@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200803241909.m2OJ9RX08326@momjian.us> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Mon, 24 Mar 2008 12:20:51 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200803/887 X-Sequence-Number: 115688 Bruce Momjian wrote: > This is an interesting observation that deserves to be discussed > separately, and relates to the patch queue. Many people want to know > what is happening with the patch queue but having better reporting > doesn't seem to help much the people who are actually processing the > queue, and requires more work. I'm not sure I follow. I tried last week to give some hours for patch review. What actually happened was that I had to wade through a ton of stuff, skipping patches that were already applied, threads that were purely discussion but not patches, threads about earlier versions of some patches. I did manage to find actual patches, but I had then to resort to my own mailbox to get the actual patch to apply and review. Now I can't be sure whether the current commitfest is finished or there are still patches pending review; what patches could use input from me; what patches I could bounce to the next commitfest. Also I don't know what patches we have for the next commitfest. I would gladly give some time to put up a Wiki page to list the patches for the next commitfest. Would that be helpful? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.