Date: Mon, 11 May 2020 22:16:53 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: PG 13 release notes, first draft
Message-ID: <20200512021653.GA971@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20200512005714.GN4666@momjian.us>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2020-May-11, Bruce Momjian wrote:

> On Mon, May 11, 2020 at 08:34:56PM -0400, Alvaro Herrera wrote:

> > Yes, we had to touch the source code in order to add documentation; but
> > so what?  Everything touches the source code, but that doesn't mean it
> > should be listed there.  I don't see what's the problem with having a
> > new subsection in the relnotes entitled "Documentation" where these two
> > items appears (glossary + new doc table format) are listed.  It's not
> > like it's going to cost us a lot of space or anything.

> 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.

IMO the table reformatting change is significant enough to be
noteworthy.  I'm suggesting that a new Documentation subsection would
list both that and the glossary, separately from Source Code -- so it'd
be E.1.3.10 and Source Code would be E.1.3.11.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services