Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 4FF759FB965 for ; Wed, 2 May 2007 15:27:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 04471-08 for ; Wed, 2 May 2007 15:27:20 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from lists.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id CABC19FB870 for ; Wed, 2 May 2007 15:27:21 -0300 (ADT) Received: from [192.168.1.50] (or-67-76-146-141.sta.embarqhsd.net [67.76.146.141]) (authenticated bits=0) by lists.commandprompt.com (8.13.7/8.13.6) with ESMTP id l42IRLJW002970; Wed, 2 May 2007 11:27:21 -0700 Message-ID: <4638D80C.5040502@commandprompt.com> Date: Wed, 02 May 2007 11:27:24 -0700 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5.0.10 (X11/20070403) MIME-Version: 1.0 To: Josh Berkus CC: pgsql-hackers@postgresql.org Subject: Re: Feature freeze progress report References: <200705021044.l42AiCJ20657@momjian.us> <200705021109.01576.josh@agliodbs.com> In-Reply-To: <200705021109.01576.josh@agliodbs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 11:27:21 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/138 X-Sequence-Number: 102740 Josh Berkus wrote: > Bruce, all, > >> No, my point is that 100% information is already available by looking at >> email archives. What we need is a short description of where we are on >> each patch --- that is a manual process, not something that can be >> automated. >> >> Tom has posted it --- tell me how we will get such a list in an >> automated manner. > > Several of us have already suggested a method. If we want the information to > be up-to-date, then the patch manager, or bug tracker, needs to be a required > part of the approval & application process, NOT an optional accessory. That > is, if patches & bug fixes can come in, get modified, get approved & applied > entirely on pgsql-patches or pgsql-bugs without ever touching the tracker > tool, then the tracker tool will be permanently out of date and useless. > > It's going to require the people who are doing the majority of the bug hunting > & patch review to change the way they work, with the idea that any extra time > associated with the new tool will be offset by being able to spread the work > more and having information easy to find later, for you as well as others. > Tom seems to be willing; are you? Hello, Well according to himself the last time this came up: http://archives.postgresql.org/pgsql-hackers/2006-08/msg01253.php No, he isn't. Sincerely, Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/