Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YyRy5-0001Md-47 for pgsql-hackers@arkaria.postgresql.org; Fri, 29 May 2015 21:37:29 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YyRy4-0004Eo-Jl for pgsql-hackers@arkaria.postgresql.org; Fri, 29 May 2015 21:37:28 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YyRy2-0004C9-TJ; Fri, 29 May 2015 21:37:27 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1YyRy0-0006SY-DK; Fri, 29 May 2015 21:37:25 +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 t4TLbD5n005001; Fri, 29 May 2015 17:37:13 -0400 From: Tom Lane To: Bruce Momjian cc: Andres Freund , Robert Haas , Stephen Frost , Magnus Hagander , "pgsql-hackers@postgresql.org" , pgsql-core Subject: Re: [CORE] postpone next week's release In-reply-to: <20150529211224.GF16602@momjian.us> 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> <20150529210459.GH26863@alap3.anarazel.de> <20150529211224.GF16602@momjian.us> Comments: In-reply-to Bruce Momjian message dated "Fri, 29 May 2015 17:12:24 -0400" Date: Fri, 29 May 2015 17:37:13 -0400 Message-ID: <5000.1432935433@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 Bruce Momjian writes: > Do we need release notes for an alpha? Once I do the release notes, it > is possible to miss subtle changes in the code that aren't mentioned in > commit messages. If the commit message isn't clear about something, you'd likely miss the issue anyway, no? Anyway, once the release notes are in the tree, we could expect that anyone committing a user-visible semantics change should update the release notes themselves. 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