X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id A39CD9FA5FC for ; Sat, 2 Sep 2006 04:00:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 51379-03 for ; Sat, 2 Sep 2006 07:00:44 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from floppy.pyrenet.fr (news.pyrenet.fr [194.116.145.2]) by postgresql.org (Postfix) with ESMTP id F32399FA5CE for ; Sat, 2 Sep 2006 04:00:40 -0300 (ADT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id 14B4C30E18; Sat, 2 Sep 2006 09:00:40 +0200 (MET DST) From: Lukas Kahwe Smith X-Newsgroups: pgsql.hackers Subject: Re: Getting a move on for 8.2 beta Date: Sat, 02 Sep 2006 09:00:35 +0200 Organization: Hub.Org Networking Services Lines: 22 Message-ID: References: <200609020036.k820aWr26205@momjian.us> <44F8DD69.6070209@dunslane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) In-Reply-To: To: pgsql-hackers@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200609/113 X-Sequence-Number: 89642 Lukas Kahwe Smith wrote: > For example I have no expertise in coding on Postgres, but I think I > would be able to collect information from this mailinglist (like specs, > url's etc.) and put them in some issue tracker or wiki. I have done > exactly the same for PHP [1] (though there are rarely specs thrown > around in PHP, so my PHP todo list is not much more than a simple bullet > list of todo's with a name and occasional URL's to additional information). Actually I should add that I went ahead and created the PHP todo list on my own, without any official blessing and one by one internals developer have joined. Now its actively used in the entire release process. This is probably the best approach to go about doing this for PostgreSQL as well. That way there is no additional work, and instead it can show if it actually helps people. And if it does more people will start to contribute to it. If not then someone who did not contribute to the code anyways wasted a bit of time to get to know the PostgreSQL todo items really well. ;) regards, Lukas