From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Detailed release notes |
Date: | 2024-07-26 13:34:47 |
Message-ID: | EC5DCAE1-E73B-4BC7-82F9-7B32BB33F15B@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jul 26, 2024, at 9:26 AM, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> wrote:
Em sex., 26 de jul. de 2024 às 10:11, Daniel Gustafsson <daniel(at)yesql(dot)se> escreveu:
That's likely the wrong level of detail for the overwhelming majority of
release notes readers. I have a feeling this was discussed not too long ago
but (if so) I fail to find that discussion now.
Wrong level ? Where is the appropriate place on DOCs to see exactly what I'll get when updated ?
A separate page "Detailed Release Notes" ? I don't think so.
I think release notes are sometimes the only place we read to decide if an upgrade is doable or not.
Well, that opened my eyes, now I can see detailed info about every feature when it's committed.
And I'm really convinced that a small link to that commit wouldn't get dirty release notes.
FWIW, pgPedia has a version of the release notes that does get that granular:
https://pgpedia.info/postgresql-versions/postgresql-17.html
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2024-07-26 13:44:41 | Re: [Proposal] Add foreign-server health checks infrastructure |
Previous Message | Marcos Pegoraro | 2024-07-26 13:25:16 | Re: Detailed release notes |