Re: Detailed release notes

On 2024-Sep-17, Bruce Momjian wrote:

> I think trying to add text to each item is both redundant and confusing,
> because I am guessing that many people will not even know what a commit
> is, and will be confused by clicking on the link.

Uh, I 100% disagree that Postgres users reading the release notes would
not know what a commit is. I think 99.9%(*) of them would know that(**).
Does a small fraction _care_ about the commit that each release note
item is related to? Sure, it's a small audience, and I think the
current implementation far too intrusive for the PDF form to be
acceptable, given that the audience is so small. But the audience is
not an empty set, so it's acceptable to have something nicer-looking.

IMO we should be looking at a more surgical approach to implement this,
perhaps using a custom SGML tag and some custom XSLT code to process
such tags that adds links the way we want, rather than generic <ulink>
tags. Or maybe <ulink> is OK if we add some class to it that XSLT knows
to process differently than generic ulinks, like func_table_entry and
catalog_table_entry.

I tend to agree with Peter that this came in way too late, and looking
at the PDF I think it should be reverted for now.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"No tengo por qué estar de acuerdo con lo que pienso"
(Carlos Caszeli)

(*) Not a scientifically-determined number

(**) You said "many people will not even know", and I said 99.9% will
know. Maybe we're both right, and if we accept both things to be true,
then we conclude that 0.01% of Postgres users is many people. Whatever
else results from this thread, I think that's a fantastic conclusion.