From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Marcos Pegoraro <marcos@f10.com.br>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Detailed release notes
Date: Fri, 26 Jul 2024 10:11:22 -0400
Message-ID: <1673965.1722003082@sss.pgh.pa.us> (raw)
In-Reply-To: <4D1ACBCD-70AD-4286-8640-6DFC2ED206B8@yesql.se>
References: <CAB-JLwZnhaAcD2g_qxSqP-zcfek8NyOU48qqneeYcjwRODr6YA@mail.gmail.com>
<F8C2CC64-5265-4668-901D-B4A20420EC89@yesql.se>
<CAB-JLwYDP58XRTjQFGswBEBHokWSh00NbvFAsAVzSQgDr+hMFg@mail.gmail.com>
<4D1ACBCD-70AD-4286-8640-6DFC2ED206B8@yesql.se>
Daniel Gustafsson <daniel@yesql.se> writes:
>> On 26 Jul 2024, at 15:00, Marcos Pegoraro <marcos@f10.com.br> wrote:
>> But why is that just a hidden comment and not a visible link for us ?
> 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.
Yeah, I too recall some discussion of surfacing the commit links
somehow, perhaps as a popup tooltip. Nobody's got round to it yet.
It's not real clear how to handle multiple links per <para>, which
happens from time to time in major release notes and just about
everyplace in minor release notes.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, daniel@yesql.se, marcos@f10.com.br
Subject: Re: Detailed release notes
In-Reply-To: <1673965.1722003082@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox