Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id 419931BFF918 for ; Fri, 6 Apr 2012 03:33:17 -0300 (ADT) Received: from moutng.kundenserver.de ([212.227.126.171]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SG2jP-0008N3-AU for pgsql-hackers@postgresql.org; Fri, 06 Apr 2012 06:33:16 +0000 Received: from [192.168.1.6] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MKKU2-1SEO2J35CY-001eea; Fri, 06 Apr 2012 08:32:58 +0200 Message-ID: <4F7E8E19.1070204@2ndQuadrant.com> Date: Fri, 06 Apr 2012 02:32:57 -0400 From: Greg Smith User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111120 Icedove/3.1.16 MIME-Version: 1.0 To: pgsql-hackers@postgresql.org Subject: Re: Last gasp References: <1333651599.31440.47.camel@hvost> <1333653659.31440.68.camel@hvost> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:j7i0p5j0y2vTn2s1c0TAwdmnFIv092cvnjqI3U3I0Io Ur8Ss+wgF/HH7NVHfRJLNr1SSTAtoeof+UI+r/zapdGbdbKVYV gliIOYvaYT/l0ORZbNGWCDHpxzQC06B6BF1MNZq/zsHYKsfciu M+wKaODN8qXmT9C1sROqiZJeRW50Z7W5oleORWaWrECLGOkDmw yQHGEp383P231np8V/Ikj8/Qm2gOr4yaoOvDe9/OboTnVZNBPD bDkbKtyUBgNhOqDpqqAnd5CkCEq2xI5ZI945C+btgrXgLGzY7s UgX54KJjUs7/7OCqsVliFUcR68wEZkI9E9IxhwkGWSC5lGNhRV tO083OtX8sFkz0tR8oIs= X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201204/302 X-Sequence-Number: 206105 On 04/05/2012 04:27 PM, Simon Riggs wrote: > It's shocking since after months of work and an especially extended > edition CF, we expect people to deliver something, not just shunt the > whole thing off as rejected with 1 days's notice to alter that > outcome. I don't think this is being fair to Robert. You agreed with the hard deadline last week. And the fact that the CF is late isn't a good reason to say it's OK for it to be more late. Every patch that had been reviewed but still had problems has been on life support the entire month of March. The surprising part isn't when one of them is finally returned, it's that they were still alive at all. The theory here is supposed to be that large patches show up in the next to last CF, and by the time they hit the last one they're close to being ready. Just since the beginning of March, Command Triggers picked up useful feedback from all three listed reviewers (plus other commentary and related committer work), going through six revisions. There was still rippling impact like the CTAS/SELECT INTO utility command work going on six weeks into the CF. The way Dimitri has been updating something this large so often makes me dizzy, and I think everyone is disappointed that we haven't seen any great subsets of this separate out to focus on. But regardless of who's right or wrong about what's left to do, any objective look at this one would say it's surely not settled down. And the bar at this point here in April isn't "is this an important feature?" anymore. It should be "is this such an important feature that it's worth delaying the release and taking a risk on recently churning code for?" Let's not kill the messenger who delivers that reminder just because the news is painful. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.com