| From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Detailed release notes |
| Date: | 2024-07-26 13:25:16 |
| Message-ID: | CAB-JLwZnA=A2LUOdR7y1yd6KexenhM-LEPWaDvfis=mh9OoDGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2024-07-26 13:34:47 | Re: Detailed release notes |
| Previous Message | Daniel Gustafsson | 2024-07-26 13:11:20 | Re: Detailed release notes |