Re: New developer papercut - Makefile references INSTALL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: New developer papercut - Makefile references INSTALL
Date
Msg-id 273569.1646693471@sss.pgh.pa.us
Whole thread Raw
In response to Re: New developer papercut - Makefile references INSTALL  (Magnus Hagander <magnus@hagander.net>)
Responses Re: New developer papercut - Makefile references INSTALL  (Robert Haas <robertmhaas@gmail.com>)
Re: New developer papercut - Makefile references INSTALL  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> But taking a step back, who is the actual audience for this? Do we
> *need* a link pointing directly there, or is it enough to just point
> to "use the docs on the web"? We can't link to the incorrect version,
> but can we just link to /docs/ and leave it at that?

Well, it's people compiling from source, so I guess we can assume some
amount of cluefulness?  I think perhaps it'd be okay to say "go here
and then navigate to the proper sub-page for your version".

> If not, could we make the change of URL a part of the branching step?
> Branch to a stable release would the include modifying README, and be
> mad ea step of version_stamp.pl?

Doesn't really help people working from git, I think, because the
master branch is always going to claim to be "devel" even when you
rewind it to some old state.  Maybe we can assume people doing
such a thing have even more clue ... but on the whole I'd rather
not add the additional complication.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Melanie Plageman
Date:
Subject: Re: make tuplestore helper function
Next
From: Zhihong Yu
Date:
Subject: Re: support for MERGE