Re: links to 12 release notes broken after branching

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, pgsql-www(at)postgresql(dot)org
Subject: Re: links to 12 release notes broken after branching
Date: 2019-09-17 17:04:11
Message-ID: 31190.1568739851@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

Andres Freund <andres(at)anarazel(dot)de> writes:
> Yes, but before the release being done we can't hand that out? So I
> don't think that's sufficient. Can't we have a rule that redirects to
> devel/release-NN.html to /NN/release-NN.html upon a 404?

That seems like it'd cause everlasting confusion about which
branch links were really meant to point at.

I'd rather see us instantiate a new release branch under
www.postgresql.org/docs/ as soon as there's a good reason to
point to it, like around beta1, or maybe when we fork the
branch in git.

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Andres Freund 2019-09-17 17:15:10 Re: links to 12 release notes broken after branching
Previous Message Andres Freund 2019-09-17 16:52:47 Re: links to 12 release notes broken after branching