From: "Jonathan S. Katz" <jkatz@postgresql.org>
Message-Id: <3070E803-B5D5-46DA-80E5-47B43BE9B085@postgresql.org>
Content-Type: multipart/signed;
 boundary="Apple-Mail=_8C0E72DD-88DE-4BF7-8F25-12000716935A";
 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 12:45:31 -0400
In-Reply-To: <19825.1533570442@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>
Precedence: bulk


--Apple-Mail=_8C0E72DD-88DE-4BF7-8F25-12000716935A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On Aug 6, 2018, at 11:47 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> "Jonathan S. Katz" <jkatz@postgresql.org> writes:
>> Though thinking on this further, we=E2=80=99d probably want to =
maintain the URLs
>> that have been generated through the years so they don=E2=80=99t all =
404 at once.
>> That would require having the appropriate URL rules written out =
either in
>> pgweb itself or at the web server level.
>=20
> 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.

I took a look at the stats and directionally it=E2=80=99s incredibly =
low. More I get
concerned by introducing 404s that could hurt any SEO-related metrics,
but that could just be general concern vs. anything factual.

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

And looking at how the docs are served, we could do this from pgweb,
which is fairly straightforward.

FWIW I=E2=80=99m 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.

Jonathan


--Apple-Mail=_8C0E72DD-88DE-4BF7-8F25-12000716935A
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/x8QSccp8cZScFAltoeysACgkQ8QSccp8c
ZSealw/8D4TMKmkGrBNZzjCkfjxszdz8JQiNmyDTVaaIRImAIvUkcahFRa6uWXNG
f4MC8fLMNYnV5/jbv0syFPAzCL61LIwHKJZrkbp0OwA/CMQkU1ZstSAwHax/IcVr
4olnQ8Afrdt05R2EdGEN2x7OmjxGq9vIgQYSVPk/O42YbtckjjGs+VlQHzkZU3pe
h8Ckrs6fS+NWh9ziySqxFQUVEe2FRoLpT/lwC3jBCZCDMvfLPbdCE1newiIlPFZR
ctBTxIc1aCADg18gEYjvdt7NYsS8iQKys06e0J69NkDyattQNnFOSlAV+qmPZBLF
I23fdmr9YavaV3mduIcfLAkmaUThTHpNuzVfAOAH9y7vR5RwDw98zPa8bT2gSKsj
KfePDcvWbVVqMdzOr18u65w2Sd7dsKFvlMRGMKgnvrM5tC3fwXKplCzatxsM0keP
xqu6aLqTuFY/qx09jblOyLF3o0ildpgJ9wl00L9nMdCjqNgcNf87ZjbswPOoMm5q
IpBO8nJUlulMDX0yotGgii3AlaT1GPJK29NjUssRrBe1iUpIr2ZQ1btMfEESNldq
GuWe+jfS8AOTuf1o0SytJn4aUL6rs5rAV9I9PkBstbtb0wWSoK9afpC8FHnFQgYy
3earyqrrXg8RdKE3WA783/OuPXtEe92AkY0w9OJOjrraCcUjr2M=
=EaiK
-----END PGP SIGNATURE-----

--Apple-Mail=_8C0E72DD-88DE-4BF7-8F25-12000716935A--