Re: Detailed release notes

On Fri, Jul 26, 2024 at 10:11 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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.
>

similar to https://docs.python.org/3/whatsnew/changelog.html

Change functions to use a safe search_path during maintenance
operations (Jeff Davis)

change to

[commitId_link1, commitId_link2]: Change functions to use a safe
search_path during maintenance operations (Jeff Davis)

Does this make sense?
If so, then we can hardcode and some automation can change to that way.