| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Detailed release notes |
| Date: | 2024-09-18 10:12:19 |
| Message-ID: | CAGECzQQgdZFjNxNaqoH6pF=-xeuJeuyhrjOqkakeQgoE3N_GOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 18 Sept 2024 at 02:55, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > Also very clutter-y. I'm not convinced that any of this is a good
> > idea that will stand the test of time: I estimate that approximately
> > 0.01% of people who read the release notes will want these links.
>
> Yes, I think 0.01% is accurate.
I think that is a severe underestimation. People that read the release
notes obviously read it because they want to know what changed. But
the release notes are very terse (on purpose, and with good reason),
and people likely want a bit more details on some of the items that
they are particularly interested in. These links allow people to
easily find details on those items. They might not care about the
actual code from the commit, but the commit message is very likely
useful to them.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2024-09-18 10:15:34 | Re: Detailed release notes |
| Previous Message | Pavel Stehule | 2024-09-18 10:11:49 | Re: Get TupleDesc for extension-defined types |