X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 02AF69FB257 for ; Sun, 3 Sep 2006 13:41:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 47452-02 for ; Sun, 3 Sep 2006 13:41:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from community1.commandprompt.com (host-130.commandprompt.net [207.173.203.130]) by postgresql.org (Postfix) with ESMTP id BB0E49FB258 for ; Sun, 3 Sep 2006 13:41:41 -0300 (ADT) Received: from [192.168.10.101] (cpe-024-211-165-134.nc.res.rr.com [24.211.165.134]) (authenticated bits=0) by community1.commandprompt.com (8.13.5.20060308/8.13.5/Debian-3ubuntu1.1) with ESMTP id k83GfU7r010024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 3 Sep 2006 09:41:32 -0700 Message-ID: <44FB05B3.3060909@dunslane.net> Date: Sun, 03 Sep 2006 12:41:23 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.6) Gecko/20060804 Fedora/1.0.4-0.5.1.fc5 SeaMonkey/1.0.4 MIME-Version: 1.0 To: Tom Lane CC: Lukas Kahwe Smith , pgsql-hackers@postgresql.org Subject: Re: Getting a move on for 8.2 beta References: <200609020036.k820aWr26205@momjian.us> <44F8DD69.6070209@dunslane.net> <2141.1157206501@sss.pgh.pa.us> In-Reply-To: <2141.1157206501@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.237 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200609/232 X-Sequence-Number: 89761 Tom Lane wrote: > Lukas Kahwe Smith writes: > >>> 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. >> > > I agree. Look at the most successful recent process change around here: > the buildfarm. Andrew Dunstan took it upon himself to make that happen. > He built it, and they came. > :-) The difference is that the buildfarm could get going with effort only from me and a handful of early adopters, while a tracker probably needs higher level of initial community buyin. Nevertheless, I take your point. > No bug/issue tracker, or anything else, is going to be successful unless > somebody commits enough time to make it so. I've noted a whole lot of > enthusiasm for having a tracker in these recent discussions, but a > remarkable shortage of individuals stepping up to do the work. > > > You are right that it will need ongoing effort. There are discussions happening about resources. Stay tuned. cheers andrew