Re: 2025-11-13 release announcement draft
| От | SAS |
|---|---|
| Тема | Re: 2025-11-13 release announcement draft |
| Дата | |
| Msg-id | 9493fbcc-8952-486f-8e80-f9b4b9124ab7@gmail.com обсуждение исходный текст |
| Ответ на | Re: 2025-11-13 release announcement draft (Justin Clift <justin@postgresql.org>) |
| Ответы |
Re: 2025-11-13 release announcement draft
|
| Список | pgsql-advocacy |
Le 10/11/2025 à 21:42, Justin Clift a écrit :
On 2025-11-11 05:01, Jonathan S. Katz wrote:Hi,
Attached is a draft of the 2025-11-13 release announcement. Please provide feedback on correctness, notable omissions no later than 2025-11-13 12:00 UTC (and ideally earlier!)
With this:
> All PostgreSQL update releases are cumulative. As with other minor releases,
> users are not required to dump and reload their database or use `pg_upgrade`
> in order to apply this update release; you may simply shutdown PostgreSQL and
> update its binaries.
>
> Users who have skipped one or more update releases may need to run additional
> post-update steps; please see the release notes from earlier versions for
> details.
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."
Is it really any better?
Best,
Stéphane
--
Dr Stéphane Schildknecht
Contact régional PostgreSQL pour l'Europe francophone
+33 617 11 37 42
В списке pgsql-advocacy по дате отправления: