Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id EEE9C9FB957 for ; Tue, 1 May 2007 17:10:13 -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 60548-02 for ; Tue, 1 May 2007 17:10:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from community1.commandprompt.com (host-254.commandprompt.net [207.173.203.254]) by postgresql.org (Postfix) with ESMTP id 26F0B9FB96B for ; Tue, 1 May 2007 17:10:11 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-135-163.nc.res.rr.com [75.177.135.163]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by community1.commandprompt.com (Postfix) with ESMTP id BFA0F1A331D; Tue, 1 May 2007 13:10:09 -0700 (PDT) Message-ID: <46379E9F.2030608@dunslane.net> Date: Tue, 01 May 2007 16:10:07 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.10) Gecko/20070301 Fedora/1.0.8-0.6.2.fc6 pango-text SeaMonkey/1.0.8 MIME-Version: 1.0 To: Josh Berkus CC: pgsql-hackers@postgresql.org Subject: Re: Feature freeze progress report References: <200705011452.l41EqPN10520@momjian.us> <200705010943.19924.josh@agliodbs.com> <46377733.3060703@postgresql.org> <200705011055.43132.josh@agliodbs.com> In-Reply-To: <200705011055.43132.josh@agliodbs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/33 X-Sequence-Number: 102635 Josh Berkus wrote: > If many people are going to block on using a web tool for submitting new > versions of a patch, claiming responsibility for review, etc., though, then > we should probably abandon this discussion right here. No new tool is going > to work if we have people who won't make any changes at all in their work > habits. > We could do most of what people want using a tracker, but that discussion always seems to end up nowhere. And, as I have noted before, use of a tracker will become a total mess unless there are adequate resources to keep it clean and up to date (e.g. to put links in items to mailing list discussions, update state etc.) So if the commercial backers of PostgreSQL want better management of the project, maybe they need to find some resources to help out. cheers andrew