Message-ID: <f6baaf95-1405-494d-932f-2f8f8b2efe05@darrenduncan.net>
Date: Mon, 1 Jun 2026 21:11:08 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: PostgreSQL 19 beta 1 release announcement draft
To: pgsql-advocacy@lists.postgresql.org
References: <ae4eb804-517d-4811-bfae-bddd1f7b7556@postgresql.org>
 <CA+TgmoZH4xH1c_epxx_+UdDnyBRi4C5Skcx2NiuyxQaNf5Egtw@mail.gmail.com>
 <8f23fd9f-ee64-4721-9cac-7c0f970fadb2@postgresql.org>
Content-Language: en-CA
From: Darren Duncan <darren@darrenduncan.net>
In-Reply-To: <8f23fd9f-ee64-4721-9cac-7c0f970fadb2@postgresql.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/f6baaf95-1405-494d-932f-2f8f8b2efe05%40darrenduncan.net>
Precedence: bulk

On 2026-06-01 7:01 p.m., Jonathan S. Katz wrote:
> The 
> difference between the announcements and the release notes is that the 
> announcements can give more context to the features and why they matter. In the 
> past, we've had issues where we've missed things that have had significant user 
> impact, so I've biased to be more verbose vs. less.
On that note, I feel the release notes are best to be a superset of the 
announcements, such that any verbiage written for announcements like the context 
and why things matter, that should be copied into the release notes so people 
reading the release notes also have that helpful information. -- Darren Duncan