| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: need xmllint on borka |
| Date: | 2014-05-02 14:38:35 |
| Message-ID: | 20140502143835.GD6018@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> (The subtext here is that borka is absolutely not an acceptable place
> to encounter documentation build failures. By the time we're at that
> stage of the release cycle, I don't really care what xmllint might
> have to say; there isn't going to be time to make it happy.)
Borka is what runs the guaibasaurus animal, so failures would show up in
buildfarm ...
If the xmllint check could be made optional, I guess we could have the
failures show up in buildfarm but avoid having them cause a problem for
"make dist" when releases are created.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-05-02 14:52:24 | Re: need xmllint on borka |
| Previous Message | Noah Misch | 2014-05-02 14:28:49 | Re: Obsolete coding in fork_process.c |