Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YzSU3-0006xC-2L for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jun 2015 16:22:39 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YzSU1-00070C-BW for pgsql-hackers@arkaria.postgresql.org; Mon, 01 Jun 2015 16:22:37 +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 1YzSU0-000701-3C; Mon, 01 Jun 2015 16:22:36 +0000 Received: from mail-bn1on0059.outbound.protection.outlook.com ([157.56.110.59] helo=na01-bn1-obe.outbound.protection.outlook.com) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1YzSTs-0004sv-0o; Mon, 01 Jun 2015 16:22:34 +0000 Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=Jim.Nasby@bluetreble.com; Received: from decina.local (198.0.242.69) by CY1PR11MB0684.namprd11.prod.outlook.com (25.163.236.22) with Microsoft SMTP Server (TLS) id 15.1.172.22; Mon, 1 Jun 2015 16:22:23 +0000 Message-ID: <556C8454.5070409@BlueTreble.com> Date: Mon, 1 Jun 2015 11:12:04 -0500 From: Jim Nasby User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Bruce Momjian , Tom Lane CC: Andres Freund , Robert Haas , Stephen Frost , Magnus Hagander , "pgsql-hackers@postgresql.org" , pgsql-core Subject: Re: [CORE] postpone next week's release References: <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> <5000.1432935433@sss.pgh.pa.us> <20150529222800.GG16602@momjian.us> In-Reply-To: <20150529222800.GG16602@momjian.us> Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [198.0.242.69] X-ClientProxiedBy: BL2PR08CA0030.namprd08.prod.outlook.com (10.255.170.148) To CY1PR11MB0684.namprd11.prod.outlook.com (25.163.236.22) X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CY1PR11MB0684; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(601004)(5005006)(520003)(3002001); SRVR:CY1PR11MB0684; BCL:0; PCL:0; RULEID:; SRVR:CY1PR11MB0684; X-Forefront-PRVS: 05947791E4 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(51704005)(377454003)(24454002)(199003)(189002)(479174004)(50986999)(50466002)(46102003)(87266999)(80316001)(54356999)(65816999)(122386002)(97736004)(65956001)(66066001)(33656002)(64706001)(65806001)(106356001)(47776003)(5001770100001)(83506001)(87976001)(40100003)(2950100001)(42186005)(59896002)(4001540100001)(64126003)(105586002)(101416001)(23746002)(189998001)(4001350100001)(68736005)(81156007)(5001960100002)(76176999)(15975445007)(62966003)(86362001)(19580395003)(5001860100001)(93886004)(36756003)(77156002)(92566002)(5001830100001)(85282002)(336755003)(18886065003); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR11MB0684; H:decina.local; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; Received-SPF: None (protection.outlook.com: bluetreble.com does not designate permitted sender hosts) X-OriginatorOrg: bluetreble.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 01 Jun 2015 16:22:23.0711 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR11MB0684 X-Pg-Spam-Score: -3.0 (---) 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 5/29/15 5:28 PM, Bruce Momjian wrote: >> could expect that anyone committing a user-visible semantics change should >> >update the release notes themselves. > Yes, that would be nice. 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.) -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Data in Trouble? Get it in Treble! http://BlueTreble.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers