Andres Freund <andres@anarazel.de> writes:
> On 2023-12-21 08:39:26 +0900, Michael Paquier wrote:
>> On Wed, Dec 20, 2023 at 11:36:28AM -0500, Tom Lane wrote:
>>> I thought the plan was to get rid of that file, in pursuit of making
>>> our distribution tarballs be more or less pure git pulls. Instead of
>>> expending more effort on it, why not just push that project forward?
> Ah, right. I don't really care what solution we go for, just that as long as
> we have INSTALL, we should make sure we don't regularly break it... Both
> Michael and I have in the last couple weeks.
So let's just do it. I think the only real question is what URL
to point at exactly. We can't simply say
https://www.postgresql.org/docs/current/installation.html
because that will be wrong for any version more than one major
release back. We could make it version-specific,
https://www.postgresql.org/docs/17/installation.html
and task src/tools/version_stamp.pl with updating it. But that's
problematic for not-yet-released branches (there's no 17 today
for example). Perhaps we can use /devel/ in the master branch
and try to remember to replace that with a version number as soon
as a release branch is forked off --- but does the docs website
get populated as soon as the branch is made?
regards, tom lane