Re: Draft release notes complete

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Stephen Frost <sfrost(at)snowman(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:33:35
Message-ID: 5048198F.8030306@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 09/05/2012 11:01 PM, Stephen Frost wrote:
> * 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?
>
>

You mean in my copious spare time?

AIUI the only thing stopping the admins from doing what is wanted is a
shortage of tuits. I suspect if we're all a tiny bit patient it will happen.

But I guess they can speak for themselves.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2012-09-06 03:43:45 Re: Re: [COMMITTERS] pgsql: Revert "commit_delay" change; just add comment that we don't hav
Previous Message Greg Smith 2012-09-06 03:20:29 Re: [repost] Help me develop new commit_delay advice