public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Evan Macbeth <[email protected]>
Cc: Peter Geoghegan <[email protected]>
Cc: PostgreSQL Advocacy <[email protected]>
Subject: Re: PostgreSQL 12: Feature Highlights
Date: Fri, 17 May 2019 10:19:30 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CACZVyo_Ws3ufpDpUmBiOOn4R5AmPmOgn5=h4UKtV64uxn8up5Q@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CAH2-WzkkJWHiY-Uqmd4L2L5YKiPDW02ach478KXb12gmFcQGtg@mail.gmail.com>
	<CACZVyo_Ws3ufpDpUmBiOOn4R5AmPmOgn5=h4UKtV64uxn8up5Q@mail.gmail.com>

On Fri, May 17, 2019 at 08:14:33AM -0400, Evan Macbeth wrote:
> Long time lurker, first time poster. :) 
> 
> 
>     80% - 90% of the items listed in the release notes aren't interesting
>     to users, but *which* 80% - 90% it is varies. The release notes don't
>     have to function as a press release, because we'll have an actual
>     press release instead.
>     --
>     Peter Geoghegan
> 
> 
> I think Peter's point here is really important. I read the release notes and
> the press releases, both, from a very different perspective than others, but I
> find both very valuable. The release notes benefit from completeness and
> detail, in my observer's opinion.

As I just stated, if the press release was exhaustive, we could have the
release notes be more detailed, but this is not the case.  I don't think
we want to get into a case where the items listed on the preess release
get a different level of detail from the items not listed.


-- 
  Bruce Momjian  <[email protected]>        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 +

view thread (63+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: PostgreSQL 12: Feature Highlights
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox