Re: Detailed release notes

On 22.08.24 19:27, Tom Lane wrote:
> Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> writes:
>> Well, a process which does this automatically would be cool, but a
>> modified version of release notes for version 17 was done manually and
>> seems fine.
>> So, why not commit this version and later for version 18 then create this
>> process ?
>
> I'd prefer to see this implemented in the website based on our
> existing markup practices. That way it would work for quite a
> few years' worth of existing release notes, not only future ones.

Seems difficult, because the annotations right now are in XML comments.
You'd need to put them in some kind of markup around it, like from

<!--
Author: Bruce Momjian <bruce(at)momjian(dot)us>
2023-09-26 [15d5d7405] pgrowlocks: change lock mode output labels for
consiste
-->

<listitem>
<para>
Change <application><xref linkend="pgrowlocks"/></application>
lock mode output labels (Bruce Momjian)
</para>
</listitem>

to

<listitem>
<para>
Change <application><xref linkend="pgrowlocks"/></application>
lock mode output labels (Bruce Momjian)
</para>
<literallayout role="something">
Author: Bruce Momjian <bruce(at)momjian(dot)us>
2023-09-26 [15d5d7405] pgrowlocks: change lock mode output labels for
consiste
</literallayout>
</listitem>

The fact that the comment is before the main item might also be a bit
tricky to sort out.