Horton

Re: Release note trimming: another modest proposal

Bruce Momjian <bruce@momjian.us>

View thread View on postgr.es
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, Magnus Hagander <magnus@hagander.net>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, pgsql-docs@lists.postgresql.org
Date: 2019-01-25T23:46:14Z
Lists: pgsql-docs 
On Fri, Jan 25, 2019 at 06:41:20PM -0500, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > I assume this means we would only keep the current release notes in the
> > git tree too, e.g. 11.0, 11.1, 11.2, etc.
> 
> Yeah, I'd imagine that each branch would have just its own release notes.
> 
> I'm not sure whether to apply this policy retroactively to the supported
> back branches or just establish it going forward.  Maintaining the notes
> could be pretty confusing for the next few years if we do the latter,
> though.

Agreed.  We would need to backpatch.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +

Commits

  1. Doc: in each release branch, keep only that branch's own release notes.