From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Jonathan S. Katz" <jkatz@postgresql.org>
cc: pgsql-docs@lists.postgresql.org
Subject: Re: Release note trimming: another modest proposal
In-reply-to: <3070E803-B5D5-46DA-80E5-47B43BE9B085@postgresql.org>
References: <19252.1533509841@sss.pgh.pa.us>
 <37D00E58-A0F0-42E4-83F1-A124A282575D@postgresql.org>
 <18020.1533568149@sss.pgh.pa.us>
 <04F6EF85-C7B7-42F3-84BC-D5670C9D77E1@postgresql.org>
 <19825.1533570442@sss.pgh.pa.us>
 <3070E803-B5D5-46DA-80E5-47B43BE9B085@postgresql.org>
Comments: In-reply-to "Jonathan S. Katz" <jkatz@postgresql.org>
	message dated "Mon, 06 Aug 2018 12:45:31 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <23296.1533574521.1@sss.pgh.pa.us>
Content-Transfer-Encoding: 8bit
Date: Mon, 06 Aug 2018 12:55:21 -0400
Message-ID: <23297.1533574521@sss.pgh.pa.us>
Precedence: bulk

"Jonathan S. Katz" <jkatz@postgresql.org> writes:
> FWIW I’m thinking of something like:

> `/docs/release-notes/release-X-Y(-Z)?.html`

> and have them all live there. Of course the docs themselves would still
> have their copy of the release notes, but we could at least have a single
> repository of all the releases, which I do see on other OSS projects.

I'm imagining this being a repo of only the obsolete branches' release
notes, not the active ones.  Otherwise we are talking about maintaining
two copies of active release note files (because of the xref problem).
I personally will flat out refuse to do that; the overhead of maintaining
the relnotes is high enough already.

Maybe you could make the website look like that without any manual effort
using a reverse redirection rule (redirecting from this new area back
into the standard docs, for pages belonging to active branches).  But that
seems pretty confusing, and prone to redirection loops if we also have the
other thing.

			regards, tom lane