Re: 2025-11-13 release announcement draft - Mailing list pgsql-advocacy

From Jonathan S. Katz
Subject Re: 2025-11-13 release announcement draft
Date
Msg-id 05bd12a3-715c-4a0d-a156-5825e6aadd85@postgresql.org
Whole thread Raw
In response to Re: 2025-11-13 release announcement draft  (SAS <sas.postgresql@gmail.com>)
List pgsql-advocacy
On 11/12/25 4:16 AM, SAS wrote:
> Le 10/11/2025 à 21:42, Justin Clift a écrit :

>> It kind of gives the impression that post-upgrade steps aren't really 
>> needed
>> unless one or more update releases have been skipped.  Not sure of better
>> wording though.
>>
> This paragraph has been used as is for many releases. I guess people who 
> have read it many times don't really think of it anymore. And I don't 
> personally thought of it as you do. Maybe we could juste turn the last 
> phrase upside down :
> 
> "Please see release notes for details on potential post-upgrade 
> steps. Users who have skipped one or more update releases may need to 
> run additional post-update steps."

Thanks for the fresh eyes on this. I thought about this a bit. For the 
current release, if there are post update steps, they are listed here, 
so I don't know if this would be confusing in that context. I've opted 
to leave the current language for now, but have been thinking on it and 
your proposed wording if we want to update it the next go-around.

Thanks!

Jonathan

Attachment

pgsql-advocacy by date:

Previous
From: SAS
Date:
Subject: Re: 2025-11-13 release announcement draft