Re: Draft release notes complete

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Draft release notes complete
Date: 2012-09-07 13:57:11
Message-ID: CABUevEyc5q+7GPrdoshQmh8VjiBj=EERR4Ws7cUAACa+zx844g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 6, 2012 at 1:06 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> On 09/05/2012 06:13 PM, Peter Eisentraut wrote:
>>
>> On 8/29/12 11:52 PM, Andrew Dunstan wrote:
>>>>>
>>>>> 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.
>>
>> Thus making the turnaround time on a docs build even slower ... ?
>
>
>
> A complete run of this process takes less than 15 minutes. And as I have
> pointed out elsewhere that could be reduced substantially by skipping
> certain steps. It's as simple as changing the command line in the crontab
> entry.

Is it possible to run it only when the *docs* have changed, and not
when it's just a code-commit? meaning, is the detection smart enough
for that?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2012-09-07 14:53:57 Re: Issue observed in cascade standby setup and analysis for same
Previous Message Pavan Deolasee 2012-09-07 13:29:06 Re: BUG #7521: Cannot disable WAL log while using pg_dump