Andres Freund <and...@anarazel.de> writes: > On 2019-02-05 12:10:57 -0500, Tom Lane wrote: >> For something like release-9-6-10.html, there's no value in having it >> appear in three or four different places. You can't even argue that >> the later branches might be more up-to-date: that text is *the same*, >> modulo toolchain-forced markup differences, in every branch; or at >> least if it isn't it means I screwed up.
> If somebody proposed adding automatic redirects from the older linked > versions to the newest /current/ URL with that version's release notes, > I'm not sure I would have argued against that. But I do *not* think > it's actually accurate they are the same - it's a significant difference > that they're linking to the corresponding version's pages, because those > will contain that version's syntax / docs. Huh? The release note contents are identical cross-branch. I know, because I'm generally the one making them. Anyway, what I'm now thinkimg would be useful would be to set up a separate area for aggregated release notes, driven off a new git repo as I suggested; and then we could consider auto-redirecting existing URLs like https://www.postgresql.org/docs/10/release-9-4-19.html into that area. regards, tom lane
