Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRdf4-0002Pg-Od for pgsql-advocacy@arkaria.postgresql.org; Fri, 17 May 2019 14:16:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hRdf3-0001uB-J0 for pgsql-advocacy@arkaria.postgresql.org; Fri, 17 May 2019 14:16:37 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRdf3-0001pD-8F for pgsql-advocacy@lists.postgresql.org; Fri, 17 May 2019 14:16:37 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRdez-0006Xh-2G; Fri, 17 May 2019 14:16:35 +0000 Received: from bruce by momjian.us with local (Exim 4.89) (envelope-from ) id 1hRdes-00071N-Sr; Fri, 17 May 2019 10:16:26 -0400 Date: Fri, 17 May 2019 10:16:26 -0400 From: Bruce Momjian To: Alvaro Herrera Cc: Peter Geoghegan , Michael Paquier , Amit Langote , David Rowley , "Jonathan S. Katz" , PostgreSQL Advocacy Subject: Re: PostgreSQL 12: Feature Highlights Message-ID: <20190517141626.5xrlllzypehrm7cy@momjian.us> References: <20190517013255.bera5dtuii376lae@momjian.us> <20190517023413.GA15079@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190517023413.GA15079@alvherre.pgsql> User-Agent: NeoMutt/20170113 (1.7.2) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, May 16, 2019 at 10:34:13PM -0400, Alvaro Herrera wrote: > On 2019-May-16, Bruce Momjian wrote: > > > The release notes are written for the _average_ reader. > > I disagree with this assertion, and frankly I cannot understand why you > think that's the most useful thing to do. The release notes are not a > press release, where you have to make things pretty or understandable to > everyone. Users can skip items they don't understand or don't care > about; but would at least be given the option. If we don't document, > we're making the decision for them that they must not care. The press release is not an exhaustive list of all features, so we can't just fall back on the press release as a way for non-internals readers to understand all the features in this release. Frankly, when I am reading a document, if I hit a few items I don't understand, I stop reading. This is why I tend to write in a generally-accessible level of detail. You can see this in all my writings, e.g., blogs. I don't know how to write differently without feeling I am being inconsiderate to the reader. Also, when I say I write for the average reader, I write for the average person who is likely to read the document, not for the average person in general. I suggest you look at how Tom Lane writes the minor release notes for an example that is better or worse than my style. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +