Re: Draft release notes complete
От | Peter Eisentraut |
---|---|
Тема | Re: Draft release notes complete |
Дата | |
Msg-id | 5047CE81.1050903@gmx.net обсуждение исходный текст |
Ответ на | Re: Draft release notes complete (Andrew Dunstan <andrew@dunslane.net>) |
Ответы |
Re: Draft release notes complete
Re: Draft release notes complete |
Список | pgsql-hackers |
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 ... ? > And the old script often broke badly, IIRC. The script broke on occasion, but the main problem was that it wasn't monitored. Which is something that could have been fixed. > The current setup doesn't install > anything if the build fails, which is a distinct improvement. You mean it doesn't build the docs if the code build fails? Would that really be an improvement?
В списке pgsql-hackers по дате отправления: