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 1hRuTL-0008Br-Tu for pgsql-advocacy@arkaria.postgresql.org; Sat, 18 May 2019 08:13:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hRuTK-00020c-4m for pgsql-advocacy@arkaria.postgresql.org; Sat, 18 May 2019 08:13:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRuTJ-00020U-P9 for pgsql-advocacy@lists.postgresql.org; Sat, 18 May 2019 08:13:37 +0000 Received: from mail-lj1-x243.google.com ([2a00:1450:4864:20::243]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hRuTD-000106-4i for pgsql-advocacy@lists.postgresql.org; Sat, 18 May 2019 08:13:36 +0000 Received: by mail-lj1-x243.google.com with SMTP id a10so8248084ljf.6 for ; Sat, 18 May 2019 01:13:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=2UPkBR189Xy88cUemLNbC80aqu7SrrM0JJ7fW84soMI=; b=WcGejcTJwSEuyKk8CPKtLmH7PikaPavh53HiEZDEHt5s54Vz/82HMgSNDDLqsXYjcr BSzMdrPYyKwEK4bsa8KH0Kns3JEnFCP5Uy6nuJTLld96clR8LC9xKkBio2DvhsZhe8PO R6TaPrX1pROa9foFjO74FClDkIiaB8vAPVhSXE2j7WRtJVe6+rVjKh008UjYbxz85X1X w3Ib7xJ1/Ff/gXLM+XiwTJD/f4bWTZNZEKMXjy8zEbwx3g99dlZeVjvMjVF3Igq3XVwE bB7qJK6b+36CjovHoZom37VebLP9TsMsKi/RPsHFJUtV3+O5VcsdbqYVW99DAqDmolfz BtVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=2UPkBR189Xy88cUemLNbC80aqu7SrrM0JJ7fW84soMI=; b=lvAr6Q22gFKifw3ZRjcCPt+8M07HlJ5+bRn3SWWJ+POjnlpTOqzocrzftjbIEEsxLK 4Y5989OgBmw0nFMEKH3O+OEITHC+KdIgqvHyFqnYArBdZV73/OL82eX3npweNRS9weYT WDshmfAjPb0L/ZsxVu//M3JsHSM3SfiPuRs6Zw0wssQhac2rMPHwAl/9aiiKZlVY/PR0 kyfR+3jHICKxc+XEUfFRflc3SNGvdgr32fdyan8eTdXGTzzRSv/SgGcI8gdBWkZDlM2p sVTzTrb5hsFZbWvJE5AhpBFEmkkYiIdIsLqCsngcXrmH7V8wdAO2yx5oYAds9YuB5GRU Sm8Q== X-Gm-Message-State: APjAAAXK6vYUWTsTcIpZp9HLnsWL/tR+dwo2Mtb/jDZynZOsrXHTk9Bx GUJ/qQj7Bn3CwY5v1aqykxNgACnXBSNSXg+nqPgjgg== X-Google-Smtp-Source: APXvYqxMUE39HQVQfN6eEG7w4GWKDqVAwVUEaOUlFwutkwx+F7d1vjXxVa198OLWAViQrVfNPB3PNUCXnU3fwyfIN5g= X-Received: by 2002:a2e:5c1:: with SMTP id 184mr22895373ljf.94.1558167208663; Sat, 18 May 2019 01:13:28 -0700 (PDT) MIME-Version: 1.0 References: <20190516182628.kbkiajfnlooocgyg@momjian.us> <20190516190806.GA14121@alvherre.pgsql> <20190517141930.735jidirzne2nlnx@momjian.us> <3e64a194-b39d-8a7b-7133-9691caaf3936@postgresql.org> In-Reply-To: <3e64a194-b39d-8a7b-7133-9691caaf3936@postgresql.org> From: Magnus Hagander Date: Sat, 18 May 2019 10:13:17 +0200 Message-ID: Subject: Re: PostgreSQL 12: Feature Highlights To: "Jonathan S. Katz" Cc: Bruce Momjian , Evan Macbeth , Peter Geoghegan , PostgreSQL Advocacy Content-Type: multipart/alternative; boundary="000000000000f931b60589251233" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000f931b60589251233 Content-Type: text/plain; charset="UTF-8" On Fri, May 17, 2019 at 4:31 PM Jonathan S. Katz wrote: > On 5/17/19 10:19 AM, Bruce Momjian wrote: > > 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. > > To step back, it's important to understand the intended goals of the > press release. > > I view the primary goal of the press release for a major version to be a > springboard to further dive into what is in the release. It helps to > give some global context to new features / changes and is an effective > "getting started" point. It needs just enough details for people to be > interested, and if they want more info, they can go to the release notes > + docs. > > The release notes then can provide additional details on what said > features (effectively a readable "diff" between versions) are, and, if > needed, the documentation can provide even greater details. > There is in fact a third layer to consider as well, which is the release announcement. This can (and sometimes are) different from the press release. So you have the press release. Then more details can be added to the release announcement. Then even more details can be added to the release notes. -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000f931b60589251233 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, May 17, 2019 at 4:31 PM Jonathan = S. Katz <jkatz@postgresql.org> wrote:
On 5/17/19 10:19 AM, Bruce Momjian wrote:
> On Fri, May 17, 2019 at 08:14:33AM -0400, Evan Macbeth wrote:
>> Long time lurker, first time poster. :)=C2=A0
>>
>>
>>=C2=A0 =C2=A0 =C2=A080% - 90% of the items listed in the release no= tes aren't interesting
>>=C2=A0 =C2=A0 =C2=A0to users, but *which* 80% - 90% it is varies. T= he release notes don't
>>=C2=A0 =C2=A0 =C2=A0have to function as a press release, because we= 'll have an actual
>>=C2=A0 =C2=A0 =C2=A0press release instead.
>>=C2=A0 =C2=A0 =C2=A0--
>>=C2=A0 =C2=A0 =C2=A0Peter Geoghegan
>>
>>
>> I think Peter's point here is really important. I read the rel= ease notes and
>> the press releases, both, from a very different perspective than o= thers, but I
>> find both very valuable. The release notes benefit from completene= ss and
>> detail, in my observer's opinion.
>
> As I just stated, if the press release was exhaustive, we could have t= he
> release notes be more detailed, but this is not the case.=C2=A0 I don&= #39;t think
> we want to get into a case where the items listed on the preess releas= e
> get a different level of detail from the items not listed.

To step back, it's important to understand the intended goals of the press release.

I view the primary goal of the press release for a major version to be a springboard to further dive into what is in the release. It helps to
give some global context to new features / changes and is an effective
"getting started" point. It needs just enough details for people = to be
interested, and if they want more info, they can go to the release notes + docs.

The release notes then can provide additional details on what said
features (effectively a readable "diff" between versions) are, an= d, if
needed, the documentation can provide even greater details.

There is in fact a third layer to consider as well, wh= ich is the release announcement. This can (and sometimes are) different fro= m the press release.

So you have the press release= . Then more details can be added to the release announcement. Then even mor= e details can be added to the release notes.

-- <= br>
--000000000000f931b60589251233--