From: Jonathan S. Katz <jkatz@postgresql.org>
To: Magnus Hagander <magnus@hagander.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-www@lists.postgresql.org <pgsql-www@lists.postgresql.org>
Subject: Re: Release Notes Archive Patch
Date: Wed, 13 Feb 2019 13:17:43 -0500
Message-ID: <36a44ed7-d3ec-f199-b604-13fafa48b91d@postgresql.org> (raw)
In-Reply-To: <CABUevEw0zxnmm_2K9HbHki3Cy5mZDYVNsGN17btwGw_8JG0PSg@mail.gmail.com>
References: <e0f09c9a-bd2b-862a-d379-601dfabc8969@postgresql.org>
<751cae66-4d83-5012-94c6-b915bfa03f9e@postgresql.org>
<23227.1550070811@sss.pgh.pa.us>
<81313189-2e85-062a-f6d9-620298b4b00e@postgresql.org>
<25885.1550074702@sss.pgh.pa.us>
<CABUevEw0zxnmm_2K9HbHki3Cy5mZDYVNsGN17btwGw_8JG0PSg@mail.gmail.com>
On 2/13/19 11:23 AM, Magnus Hagander wrote:
> On Wed, Feb 13, 2019 at 5:18 PM Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>> wrote:
>
> "Jonathan S. Katz" <jkatz@postgresql.org
> <mailto:jkatz@postgresql.org>> writes:
> > On 2/13/19 10:13 AM, Tom Lane wrote:
> >> The patch doesn't convey a lot to my mind, so I have to ask: exactly
> >> what URLs would this present?
>
> > I'm a bit confuse by the question, so I'll answer it from two angles.
>
> Neither of those are quite what I meant. As I understood Andres'
> complaint, it was that right now we have URLs like
>
> https://www.postgresql.org/docs/10/release-9-6-5.html
>
> but those are going to be 404 beginning tomorrow. It sounds from your
> response like this patch isn't meant to restore those cross-version
> URLs.
> Which is fine by me, really, but we might get pushback about it. If so,
> there might be material for follow-on work to redirect those into this
> new set of URLs.
>
>
> We can make those become redirects at the webserver level, I'm pretty
> sure. Seems like it should be easy enough to regexp-match it for a
> simple mapping.
+1; I would question whether or not its worth it, but we do have that
option.
>
> I'm less certain if we can have that tested and deployed by tomorrow.
> (Which goes for the whole patch from Jonathan as well)
I will profess confidence with the patch -- of course, I would
appreciate additional validation (and I'm there are different approaches
as well, given I put forward one back in the summer :)
If we want to push it, I'm ok to own it and be available for any fixes
(which is easier now that I'm in one place for awhile, and given it's
release day I try to stay around).
Thanks,
Jonathan
Attachments:
[application/pgp-signature] signature.asc (832B, ../36a44ed7-d3ec-f199-b604-13fafa48b91d@postgresql.org/2-signature.asc)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-www@postgresql.org
Cc: jkatz@postgresql.org, magnus@hagander.net, tgl@sss.pgh.pa.us, pgsql-www@lists.postgresql.org
Subject: Re: Release Notes Archive Patch
In-Reply-To: <36a44ed7-d3ec-f199-b604-13fafa48b91d@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox