Re: PG 13 release notes, first draft - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PG 13 release notes, first draft
Date
Msg-id 11843.1589250233@sss.pgh.pa.us
Whole thread Raw
In response to Re: PG 13 release notes, first draft  (Bruce Momjian <bruce@momjian.us>)
Responses Re: PG 13 release notes, first draft
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Well, are you suggesting a new section because the glossary shouldn't be
> listed under source code, or because you want the function reformatting
> added?  We just need to understand what the purpose is.  We already have
> the glossary listed, since that is new and user-visible.

The implication of what you say here is that "is it user-visible?"
is a criterion for whether to release-note something.  By that logic
we probably *should* relnote the function table layout changes, because
they sure as heck are user-visible.  People might or might not notice
addition of a glossary, but I think just about every user consults
the function/operator tables regularly.

I concur with Alvaro's position that if we are listing documentation
changes, pushing them under "Source Code" is not the way to do it.
That subsection has always been understood to be "stuff you don't
care about if you're not a hacker".

So that sort of leads me to the conclusion that "major documentation
changes" might be a reasonable sub-heading for the release notes.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: PG 13 release notes, first draft
Next
From: Robert Haas
Date:
Subject: Re: No core file generated after PostgresNode->start