Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YyRSp-0008JA-3W for pgsql-hackers@arkaria.postgresql.org; Fri, 29 May 2015 21:05:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YyRSo-0003nd-Io for pgsql-hackers@arkaria.postgresql.org; Fri, 29 May 2015 21:05:10 +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 1YyRSl-0003iF-4B; Fri, 29 May 2015 21:05:07 +0000 Received: from mail.anarazel.de ([217.115.131.40]) by magus.postgresql.org with esmtp (Exim 4.84) (envelope-from ) id 1YyRSh-0004wp-VA; Fri, 29 May 2015 21:05:06 +0000 Received: from intern.anarazel.de (unknown [184.23.178.130]) (Authenticated sender: andres@anarazel.de) by mail.anarazel.de (Postfix) with ESMTPSA id 535CD860004; Fri, 29 May 2015 23:05:02 +0200 (CEST) Date: Fri, 29 May 2015 23:04:59 +0200 From: Andres Freund To: Tom Lane Cc: Robert Haas , Stephen Frost , Bruce Momjian , Magnus Hagander , "pgsql-hackers@postgresql.org" , pgsql-core Subject: Re: [CORE] postpone next week's release Message-ID: <20150529210459.GH26863@alap3.anarazel.de> References: <20150529185431.GG26667@tamriel.snowman.net> <26984.1432927977@sss.pgh.pa.us> <20150529195609.GD16602@momjian.us> <20150529195751.GN26667@tamriel.snowman.net> <27697.1432929660@sss.pgh.pa.us> <28477.1432931820@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <28477.1432931820@sss.pgh.pa.us> X-Pg-Spam-Score: -4.2 (----) 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 On 2015-05-29 16:37:00 -0400, Tom Lane wrote: > Well, maybe we ought to call it an alpha not a beta, but I think we ought > to put out some kind of release that we can encourage people to test. I also do think it's important that we put out a beta (or alpha) relatively soon. Both because we actually need input to find out what works and what doesn't and also because it pushes us to tie up loose ends. A beta with open items isn't that bad a thing? There's many bigger projects doing 4-8 betas releases before a major one; and most of them have open items at the indvidual beta's release times. I think we should define/document it so that there's no hard goal of being compatible for beta releases and that the compatibility goal starts with the first release candidate, and not the betas. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers