Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id EFB9D63310A for ; Fri, 5 Jun 2009 10:51:46 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 41794-04 for ; Fri, 5 Jun 2009 10:51:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by mail.postgresql.org (Postfix) with ESMTP id A918A63307B for ; Fri, 5 Jun 2009 10:51:41 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-154-027.nc.res.rr.com [::ffff:75.177.154.27]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Fri, 05 Jun 2009 09:51:17 -0400 id 0008078D.4A2922D5.000063BD Message-ID: <4A2922E8.1090505@dunslane.net> Date: Fri, 05 Jun 2009 09:51:36 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: Tom Lane CC: Markus Wanner , Ron Mayer , Marko Kreen , Greg Stark , Andres Freund , Aidan Van Dyk , Heikki Linnakangas , Magnus Hagander , PostgreSQL-development Subject: Re: PostgreSQL Developer meeting minutes up References: <20090526144812.GC15213@yugib.highrise.ca> <20090602162333.369974jcc3jpn3dx@mail.bluegap.ch> <20090602180702.15986cp384yo3l7q@mail.bluegap.ch> <20090603131004.12934iyrr4f7rlsc@mail.bluegap.ch> <4136ffa0906030508i2971790dk54a8203ee03ed196@mail.gmail.com> <4A266A56.2020703@anarazel.de> <4136ffa0906030701x200bf0e4o4c77fa3239062ca5@mail.gmail.com> <20090604114610.808217tbogts0noi@mail.bluegap.ch> <4A283A8D.8030600@cheapcomplexdevices.com> <20090605090514.11712ntlvhi2deay@mail.bluegap.ch> <2871.1244209112@sss.pgh.pa.us> In-Reply-To: <2871.1244209112@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.093 tagged_above=0 required=5 tests=AWL=0.093 X-Spam-Level: X-Archive-Number: 200906/467 X-Sequence-Number: 139522 Tom Lane wrote: > "Markus Wanner" writes: > >> Note that a requirement for daggy fixes is that "the bug is fixed >> close to the point where it was introduced". So fixing it on the >> oldest stable branch that introduced a bug instead of fixing it on >> HEAD and then back-porting would certainly be a step into the right >> direction. >> > > I think it's already been made crystal clear that the people who > actually do this work don't do it that way, and are uninterested in > allowing their tools to force them to do it that way. Patching from > HEAD back works better for us for a number of reasons, the main one > being that HEAD is the version of the code that's most "swapped into" > our awareness. > Yeah, a requirement to work from the back branch forward is quite unacceptable IMNSHO. It's also quite unreasonable. The tool is there to help, not to force an unnatural work pattern on us. cheers andrew