Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 85F9F9FBB3B for ; Wed, 2 May 2007 10:29:29 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 23410-01 for ; Wed, 2 May 2007 10:29:13 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id B6ACC9FB932 for ; Wed, 2 May 2007 10:29:18 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-221-217-243.bk12-dsl.surnet.cl [201.221.217.243]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l42DSVGp026148; Wed, 2 May 2007 06:28:32 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 6ACB732A10; Wed, 2 May 2007 09:28:29 -0400 (CLT) Date: Wed, 2 May 2007 09:28:29 -0400 From: Alvaro Herrera To: Andrew Dunstan Cc: Tom Lane , Josh Berkus , pgsql-hackers@postgresql.org Subject: Re: Feature freeze progress report Message-ID: <20070502132829.GE4585@alvh.no-ip.org> Mail-Followup-To: Andrew Dunstan , Tom Lane , Josh Berkus , pgsql-hackers@postgresql.org References: <200705012309.l41N9O908241@momjian.us> <200705012151.51915.josh@agliodbs.com> <5678.1178083185@sss.pgh.pa.us> <4638851C.9060308@dunslane.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4638851C.9060308@dunslane.net> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: ClamAV version 0.88.5, clamav-milter version 0.88.5 on projects.commandprompt.com X-Virus-Status: Clean X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (lists.commandprompt.com [192.168.2.159]); Wed, 02 May 2007 06:28:32 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/117 X-Sequence-Number: 102719 Andrew Dunstan wrote: > > > Tom Lane wrote: > >So in a roundabout way we come back > >to the idea that we need a bug tracker (NOT a patch tracker), plus > >people putting in the effort to make sure it stays a valid source > >of up-to-date info. Without the latter it won't really be useful. > > Hallelujah Brother! Amen > BTW, a bug tracker can be used as a patch tracker, although the reverse > isn't true. For example, the BZ people use BZ that way, in fact - most > patches arrive as attachments to bugs. And trackers can be used just as > well for tracking features as well as bugs. The pidgin (previously known as Gaim) guys also use it that way. They add a bug for each thing they want to change, even new features, and track the patches in there. Then they have a list of issues that should be solved for each release, so it's easy to see which ones are still missing using their Trac interface. http://developer.pidgin.im/roadmap So the status email that Tom sent yesterday would be a very simple thing to generate, just looking at the "bugs to fix" page. I'm not saying we should use Trac, mainly because I hate how it (doesn't) interact with email. But it does say that a bug tracker can be useful to us. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.