On Friday 13 October 2006 16:59, Fredrik Lundh wrote: > yeah, but *you* are doing it. if the server did that, Martin and > other trusted contributors could upload the files as soon as they're > available, instead of first transferring them to you, and then waiting > for you to find yet another precious time slot to spend on this release. Sure - I get that. There's a couple of reasons for me doing it. First is gpg signing the release files, which has to happen on my local machine. There's also the variation in who actually builds the releases; at least one of the Mac builds was done by Bob I. But there could be ways around this. I don't want to have to ensure every builder has scp, and I'd also prefer for it to all "go live" at once. A while back, the Mac installer would follow up "some time" after the Windows and source builds. Every release, I'd get emails saying "where's the mac build?!" > > The problems are with the other bits of the pages. I keep thinking "next > > release, I'll automate it further", but never have time on the day. > > that's why you have to have an overall infrastructure that lets you make > incremental tweaks to the tool chain, so things can get a little better > all the time. Pyramid obviously isn't such a system. I can't disagree with this. -- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4