Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id B1DF7640595 for ; Sat, 6 Jun 2009 15:16:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 04608-01-3 for ; Sat, 6 Jun 2009 15:16:31 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from exprod7og115.obsmtp.com (exprod7og115.obsmtp.com [64.18.2.217]) by mail.postgresql.org (Postfix) with SMTP id 1396B64055F for ; Sat, 6 Jun 2009 15:15:51 -0300 (ADT) Received: from source ([209.85.220.207]) by exprod7ob115.postini.com ([64.18.6.12]) with SMTP ID DSNKSiqyVoM/4HGAPpbU277nxl2ZG8W4gi+z@postini.com; Sat, 06 Jun 2009 11:15:55 PDT Received: by fxm3 with SMTP id 3so730130fxm.40 for ; Sat, 06 Jun 2009 11:15:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.110.211 with SMTP id o19mr2726268fap.57.1244312149607; Sat, 06 Jun 2009 11:15:49 -0700 (PDT) In-Reply-To: <4888.1244216273@sss.pgh.pa.us> References: <20090526144812.GC15213@yugib.highrise.ca> <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> <603c8f070906050829m1eaaa969tff7ca85d04018c5a@mail.gmail.com> <4888.1244216273@sss.pgh.pa.us> Date: Sat, 6 Jun 2009 19:15:49 +0100 Message-ID: <4136ffa0906061115p1ff2ac36hebad6774a4e31bed@mail.gmail.com> Subject: Re: PostgreSQL Developer meeting minutes up From: Greg Stark To: Tom Lane Cc: Robert Haas , Markus Wanner , Ron Mayer , Marko Kreen , Andres Freund , Aidan Van Dyk , Heikki Linnakangas , Magnus Hagander , Andrew Dunstan , PostgreSQL-development Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200906/523 X-Sequence-Number: 139578 On Fri, Jun 5, 2009 at 4:37 PM, Tom Lane wrote: > > However, given that we don't do any real development on the back > branches, it might be that trying to be smart about this is a waste of > time anyway. =A0Surely only the HEAD version of the patch is going to be > something that other developers care about merging with. For what it's worth that's certainly not true. Any user maintaining a patched version of the source tree for production use will want to merge in any patches for older releases. For example anyone using the CONNECT BY patch with 8.3 will surely want to take any 8.3 patch releases. Of course EDB in particular has to maintain sources based on old patch releases as well as the current branch. That said, I don't see that this really affects the decision here. These devleopers will just merge in the patch as it was applied to the back branch anyways. --=20 greg