Re: Release note trimming: another modest proposal
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: Magnus Hagander <magnus@hagander.net>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-docs@lists.postgresql.org
Date: 2019-01-25T23:31:11Z
Lists: pgsql-docs
On Mon, Jan 7, 2019 at 09:18:29PM -0500, Jonathan Katz wrote: > So circling back on this, Peter's point makes a lot of sense. > > If you want to see release notes for other major versions, there would > be URLs to the other major versions, but that would be far less costly > than keeping the actual release notes in each tarball. 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. -- 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
-
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