Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M274529=pgsql-hackers-arkari@postgresql.org>)
 id 1YzSdj-0007Ie-OU
 for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jun 2015 16:32:39 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-hackers-owner+M274529=pgsql-hackers-arkari@postgresql.org>)
 id 1YzSdj-0000Ka-8L
 for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jun 2015 16:32:39 +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 <tgl@sss.pgh.pa.us>)
 id 1YzSdi-0000KO-DL; Mon, 01 Jun 2015 16:32:38 +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 <tgl@sss.pgh.pa.us>)
 id 1YzSdf-00054M-QN; Mon, 01 Jun 2015 16:32:37 +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 t51GWLeV025638;
 Mon, 1 Jun 2015 12:32:22 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jim Nasby <Jim.Nasby@bluetreble.com>
cc: Bruce Momjian <bruce@momjian.us>, Andres Freund <andres@anarazel.de>,
 Robert Haas <robertmhaas@gmail.com>, Stephen Frost <sfrost@snowman.net>,
 Magnus Hagander <magnus@hagander.net>,
 "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
 pgsql-core <pgsql-core@postgresql.org>
Subject: Re: [CORE] postpone next week's release
In-reply-to: <556C8454.5070409@BlueTreble.com>
References: 
 <CABUevExb+p3OGFBAMTc2s0tuuygkmnca_BV6Qe0hACvRmgyb1w@mail.gmail.com>
 <26984.1432927977@sss.pgh.pa.us> <20150529195609.GD16602@momjian.us>
 <20150529195751.GN26667@tamriel.snowman.net> <27697.1432929660@sss.pgh.pa.us>
 <CA+Tgmoadg9dHLpWodfwDaTZ=RbW+C_4CrgYyZ=Vx5QpMyP=N5A@mail.gmail.com>
 <28477.1432931820@sss.pgh.pa.us> <20150529210459.GH26863@alap3.anarazel.de>
 <20150529211224.GF16602@momjian.us> <5000.1432935433@sss.pgh.pa.us>
 <20150529222800.GG16602@momjian.us> <556C8454.5070409@BlueTreble.com>
Comments: In-reply-to Jim Nasby <Jim.Nasby@bluetreble.com>
 message dated "Mon, 01 Jun 2015 11:12:04 -0500"
Date: Mon, 01 Jun 2015 12:32:21 -0400
Message-ID: <25637.1433176341@sss.pgh.pa.us>
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-hackers>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-hackers.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@postgresql.org>
List-Post: <mailto:pgsql-hackers@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-hackers>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
X-Mailing-List: pgsql-hackers
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Jim Nasby <Jim.Nasby@bluetreble.com> writes:
> FWIW, I've always wondered why we don't create an empty next-version 
> release notes as part of stamping a major release and expect patch 
> authors to add to it. I realize that likely creates merge conflicts, but 
> that seems less work than doing it all at the end. (Or maybe each patch 
> just creates a file and the final process is pulling all the files 
> together.)

There are good reasons to write the release notes all in one batch:
otherwise you don't get any uniformity of editorial style.

			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