public inbox for pgsql-advocacy@postgresql.org  

help / color / mirror / Atom feed

From: Jonathan S. Katz <jkatz@postgresql.org>
To: SAS <sas.postgresql@gmail.com>
To: pgsql-advocacy@lists.postgresql.org
Subject: Re: 2025-11-13 release announcement draft
Date: Thu, 13 Nov 2025 09:17:54 -0500
Message-ID: <05bd12a3-715c-4a0d-a156-5825e6aadd85@postgresql.org> (raw)
In-Reply-To: <9493fbcc-8952-486f-8e80-f9b4b9124ab7@gmail.com>
References: <dc8bcdf1-1402-4b42-bbaa-9a6f810660b0@postgresql.org>
	<abc4e4e658e230993e9623fc083e9965@postgresql.org>
	<9493fbcc-8952-486f-8e80-f9b4b9124ab7@gmail.com>

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


Attachments:

  [application/pgp-signature] OpenPGP_signature.asc (840B, 2-OpenPGP_signature.asc)
  download

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: pgsql-advocacy@postgresql.org
  Cc: jkatz@postgresql.org, sas.postgresql@gmail.com, pgsql-advocacy@lists.postgresql.org
  Subject: Re: 2025-11-13 release announcement draft
  In-Reply-To: <05bd12a3-715c-4a0d-a156-5825e6aadd85@postgresql.org>

* 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