Re: Release note trimming: another modest proposal
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
Cc: pgsql-docs@lists.postgresql.org
Date: 2018-08-06T15:47:22Z
Lists: pgsql-docs
"Jonathan S. Katz" <jkatz@postgresql.org> writes: > Though thinking on this further, we’d probably want to maintain the URLs > that have been generated through the years so they don’t all 404 at once. > That would require having the appropriate URL rules written out either in > pgweb itself or at the web server level. I dunno, you think it's worth the trouble? The whole premise of this proposal is that hardly anybody is looking at those pages. If that's not the case, we shouldn't be doing this. OTOH, if we can easily set up a generic redirect rule like "if https://www.postgresql.org/docs/*/static/release-*.html doesn't exist, then redirect to https://www.postgresql.org/docs/old-release-notes/static/release-*.html" it might be worth doing. 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