Re: Draft release notes complete

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Draft release notes complete
Date: 2012-09-06 03:01:56
Message-ID: 20120906030156.GM1267@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Andrew Dunstan (andrew(at)dunslane(dot)net) wrote:
> The buildfarm code does not run if there are no changes. The job
> runs, sees that there are no changes, and exits.

Right, hence it makes great sense to use it for this (as opposed to
Bruce's previous script or some other new one). While it might appear
to be overkill, it actually does lots of useful and good things and
integrates better with the existing setup anyway.

Now that you've provided the magic sauce wrt --skip-steps, can we get an
admin to implement a doc-only build that runs more frequently to update
the dev docs..?

Andrew, if we're going to rely on that, even just internally, perhaps we
should go ahead and add documentation for it?

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2012-09-06 03:14:15 Re: too much pgbench init output
Previous Message Bruce Momjian 2012-09-06 02:57:06 Re: 9.2 pg_upgrade regression tests on WIndows