Re: Draft release notes complete
От | Magnus Hagander |
---|---|
Тема | Re: Draft release notes complete |
Дата | |
Msg-id | CABUevEyc5q+7GPrdoshQmh8VjiBj=EERR4Ws7cUAACa+zx844g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Draft release notes complete (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Draft release notes complete
|
Список | pgsql-hackers |
On Thu, Sep 6, 2012 at 1:06 AM, Andrew Dunstan <andrew@dunslane.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 HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: