On Tue, Sep 17, 2024 at 03:29:54PM -0300, Marcos Pegoraro wrote:
> Em ter., 17 de set. de 2024 às 05:12, Alvaro Herrera <alvhe...@alvh.no-ip.org>
> escreveu:
>
> Add backend support for injection points (Michael Paquier) [commit 1] [2]
> [3] [4]
>
> I think this way would be fine.
>
> And it would be good to have a
> target="_blank"
> on commit links so a new window or tab would be opened instead of going back
> and forth.
> This way you can open these 4 links and then navigate on them to see exactly
> what was done on every commit.
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.
What I have done is to add text to the top of "Appendix E. Release
Notes" explaining the symbol and what it links to. Patch attached.
We can still consider a different symbol or number labeling, but I think
this patch is in the right direction.
--
Bruce Momjian <br...@momjian.us> https://momjian.us
EDB https://enterprisedb.com
When a patient asks the doctor, "Am I going to die?", he means
"Am I going to die soon?"
diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index cf6ba540876..8d408a50eb1 100644
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -69,6 +69,15 @@ For new features, add links to the documentation sections.
review, so each item is truly a community effort.
</para>
+ <para>
+ Section markers (§) in the release notes link to <ulink
+ url="https://git.postgresql.org/gitweb/?p=postgresql.git";><application>gitweb</application></ulink>
+ pages which show the primary <application>git</application> commit
+ messages and source tree changes responsible for the release note item.
+ There might be additional <application>git</application> commits which
+ are not shown.
+ </para>
+
<!--
When beginning a new major-release series, create a new release-NN.sgml
file, removing the previous one, and change the &-reference here.
