| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: documentation is now XML |
| Date: | 2017-11-28 17:27:21 |
| Message-ID: | f4bc5cb6-547e-0cfe-a41c-19b02adfe51e@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/28/2017 12:06 PM, Tom Lane wrote:
>
> One thing we'd definitely better do is enable some buildfarm coverage.
> AFAIK, the only buildfarm animal that's building the docs is guaibasaurus,
> and it only seems to be doing that on HEAD. Since this has considerably
> increased the risks of back-patching creating busted docs in the back
> branches, we'd better spin up some back-branch testing as well.
>
>
crake builds the docs on all branches pretty regularly. I have changed
its config so it builds them pretty much every build.
Of course, it's only building the HTML docs. Do we need more than that?
Continuously making PDFs seems a bit excessive.
cheers
andrew
--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-11-28 17:35:00 | Re: [HACKERS] postgres_fdw bug in 9.6 |
| Previous Message | Tom Lane | 2017-11-28 17:06:36 | Re: documentation is now XML |