Horton

Re: Draft release notes complete

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Bruce Momjian <bruce@momjian.us>, Magnus Hagander <magnus@hagander.net>, Tom Lane <tgl@sss.pgh.pa.us>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-08-30T03:52:58Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Expose track_iotiming information via pg_stat_statements.

  2. Rewrite GiST support code for rangetypes.

  3. Clean up a couple of box gist helper functions.

  4. Replace the "New Linear" GiST split algorithm for boxes and points with a

On 08/29/2012 11:20 PM, Peter Eisentraut wrote:
> On Wed, 2012-08-29 at 22:23 -0400, Alvaro Herrera wrote:
>>>>> Where are we on building the development docs more frequently?
>>>> Still waiting for details on how it works to set that up on the
>>>> buildfarm client.
>>> Where are we on this?
>> Waiting on Andrew.
>>
>> As far as I can see, we need to update the machine to release 4.7, and
>> then install a "skip file" or something like that.  Andrew, can you
>> please explain how is that to be used?  I don't see it documented
>> anywhere.
> Why does this need to be tied into the build farm?  Someone can surely
> set up a script that just runs the docs build at every check-in, like it
> used to work.  What's being proposed now just sounds like a lot of
> complication for little or no actual gain -- net loss in fact.
>
>

It doesn't just build the docs. It makes the dist snapshots too. And the 
old script often broke badly, IIRC. The current setup doesn't install 
anything if the build fails, which is a distinct improvement. And you 
can see the causes of any failure via the buildfarm logs.

But I don't really have any stake in this, I just created a tiny Module 
to help Magnus do what he wanted.

In answer to Alvaro's question, you can disable most steps via a command 
line switch --skip-steps, the value of which is a space separated list 
of names. I haven't documented it mainly because it was really developed 
for use in development. The allowed values are:

    install
    make
    make-doc
    install
    make-contrib
    install
    install-check
    contrib-install-check
    pl-install-check
    isolation-check
    check
    ecpg-check



cheers

andrew