From: "Jonathan S. Katz" <jkatz@postgresql.org>
Message-Id: <D760BC11-6F2D-4E5D-A6FB-ADC4CA5C9B84@postgresql.org>
Content-Type: multipart/signed;
 boundary="Apple-Mail=_A7998388-80A2-4022-A94E-76D72BB369E8";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Release note trimming: another modest proposal
Date: Mon, 6 Aug 2018 13:22:57 -0400
In-Reply-To: <23297.1533574521@sss.pgh.pa.us>
Cc: pgsql-docs@lists.postgresql.org
To: Tom Lane <tgl@sss.pgh.pa.us>
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>
 <23297.1533574521@sss.pgh.pa.us>
Precedence: bulk


--Apple-Mail=_A7998388-80A2-4022-A94E-76D72BB369E8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Aug 6, 2018, at 12:55 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> "Jonathan S. Katz" <jkatz@postgresql.org> writes:
>> FWIW I=E2=80=99m thinking of something like:
>=20
>> `/docs/release-notes/release-X-Y(-Z)?.html`
>=20
>> 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.
>=20
> 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.

Well I want to make this easier, not harder. Thinking about the process =
of
maintaining all, no matter what, I see making it more complicated for =
someone,
so I will drop that for now.

> 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.

Agreed.

So perhaps `/docs/archive/release-notes/release-X-Y-(-Z)?.html` will be =
where
they live.

I can make a quick prototype of this on pgweb just to see how easy it is =
to get
the release notes up in it. Basically, once the archived ones are in =
pgweb, we
would not need to have to build them anymore.

Jonathan


--Apple-Mail=_A7998388-80A2-4022-A94E-76D72BB369E8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE+oS2la8r95ogZD/x8QSccp8cZScFAltog/EACgkQ8QSccp8c
ZSclJQ//YCo9OUpJVuB+7ZSzzC/WXYwvGoz2hh7clsCm+2H7FYzepJRfTUIr6iiX
pKWhx74loMnbPhfaBdRLuaF3avDTO8yBhfBWflt4xWnP/uXXzYiJkuVQTlTDCzue
1YFwBfp3RW2+hnhaQVilIevnGpbAdK00t//+d2NU82e8QQkgJmI1K8X1e0Bd5xKu
nqm03EApgmmDa/9u28T5+LDx+4hlg1TTdhcUBX24haqzreE9linRYpyLyqdExcZQ
hNq9QJMpvqgDridq7vokLcdzRDwzN08r14Q746QnzvU/pocwqZAgxJ9FuQsafeAb
7ufQNTCMUcVJetk6TIyevSVVBw+2/agHoeSahbKAE7g0nk6speX6ZIFC++vwXELA
lmo1AkumT9/x4UCZlcuTuux43dRaEQf85v7SY9xRZMmoa1a/OSvET7JTdshTl0+5
uEfVYu+SuMQE/MptmFbqy9LbSq4nHVa3sjv7q8CBr45o3spgArSUuDPfU0rHMJXS
LVK+CF/VGf3pHwN6vGW+5uFc3yyftFnD2W0ymoH26QrLlKRpK/6FIPlz0EkLydnA
kj0Ck6oAgDsWuIJ/TLvx5fssamxdYMt2PNvACy3HGj9IxFc7fM+UoIXNnHvt3d41
weCOKyp5klce90mfQArwKpxOVIgTYmDzCc6LfTQmqSBFWU8pWzw=
=4uvG
-----END PGP SIGNATURE-----

--Apple-Mail=_A7998388-80A2-4022-A94E-76D72BB369E8--