Re: Release note trimming: another modest proposal
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.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:41:20Z
Lists: pgsql-docs
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. regards, tom lane
Commits
-
Doc: in each release branch, keep only that branch's own release notes.
- ed64db588a67 9.5.16 landed
- bb428cb11722 9.4.21 landed
- 60b1d6c2a736 9.6.12 landed
- 2b24271153ec 10.7 landed
- 0d13dd371b64 11.2 landed
- 527b5ed1ad46 12.0 landed