| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:15:10 |
| Message-ID: | 20190917171510.dtuii6v2ikxksows@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Hi,
On 2019-09-17 13:04:11 -0400, Tom Lane wrote:
> 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.
Howso? There'll only be one release-NN file across all branches? Leaving
aside the time where docs are regenerated etc?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2019-09-17 17:50:40 | Re: links to 12 release notes broken after branching |
| Previous Message | Tom Lane | 2019-09-17 17:04:11 | Re: links to 12 release notes broken after branching |