Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YyQ2C-0002dh-T9 for pgsql-hackers@arkaria.postgresql.org; Fri, 29 May 2015 19:33:37 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YyQ2B-0000Nr-CK for pgsql-hackers@arkaria.postgresql.org; Fri, 29 May 2015 19:33:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YyQ1g-000864-Jy; Fri, 29 May 2015 19:33:04 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1YyQ1c-00036U-P7; Fri, 29 May 2015 19:33:03 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id t4TJWvhW026985; Fri, 29 May 2015 15:32:57 -0400 From: Tom Lane To: Magnus Hagander cc: Stephen Frost , Robert Haas , "pgsql-hackers@postgresql.org" , pgsql-core Subject: Re: [CORE] postpone next week's release In-reply-to: References: <20150529185431.GG26667@tamriel.snowman.net> Comments: In-reply-to Magnus Hagander message dated "Fri, 29 May 2015 21:11:01 +0200" Date: Fri, 29 May 2015 15:32:57 -0400 Message-ID: <26984.1432927977@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Magnus Hagander writes: > On Fri, May 29, 2015 at 8:54 PM, Stephen Frost wrote: >> I just caution that we appreciate PGCon coming up and that we do our >> best to avoid running into a case where we have to push it further due >> to everyone being at the conference. > If we plan it, we certainly *can* make a release during pgcon. If that's > what the reasonable timing comes down to, I think getting these fixes out > definitely has to be considered more important than the conference, so a > few of us will just have to take a break... I think there's no way that we wait more than one additional week to push the fsync fix. So the problem is not with scheduling the update releases, it's with whether we can also fit in a 9.5 beta release before PGCon. (I can't see doing a beta *during* PGCon week. I for one am going to be on an airplane at the time I'd normally have to be Doing Release Stuff.) I know Josh doesn't like to do beta1 releases concurrently with back branches because it confuses the PR messaging. But we could make an exception perhaps; or do all those releases the same week but announce the beta the day after the bugfix releases. Or we just let the beta slide till after PGCon, but then I think we're missing some excitement factor. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers