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: Chris Travers <chris.travers@gmail.com>, pgsql-docs@lists.postgresql.org
Date: 2018-08-09T02:35:31Z
Lists: pgsql-docs
Bruce Momjian <bruce@momjian.us> writes: > Works for me, though, is there no interest in keeping the SGML files in > the git tree and just not building them as docs? Yeah, I thought about that alternative, but I'm not sure I see the percentage. It'd bloat the tarballs compared to removing them, and for what? Another point that's bothered me a bit is that we're failing to keep the historical notes historical. Every so often, somebody decides they need to run around and fix misspellings or whatever, and they do it to the old notes as well as stuff that's current. To me that goes against every principle of archiving. Taking old notes files out of the tree once we've stopped updating them would at least put a limit on how long they're exposed to historical revisionism. 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