<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Apr 19, 2014, at 7:56 PM, Nick Coghlan <<a href="mailto:ncoghlan@gmail.com">ncoghlan@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p dir="ltr"><br>
On 19 Apr 2014 18:52, "David Wilson" <<a href="mailto:dw%2Bpython-ideas@hmmz.org">dw+python-ideas@hmmz.org</a>> wrote:<br>
><br>
> Finally it's not obvious to me that this is absolutely a good idea, however I'm willing to argue for it for as long as I'm procrastinating on setting up my own Jenkins install :-P</p><p dir="ltr">I actually think it's a good idea, I'd just like to approach the idea indirectly by building out CPython's test infrastructure further first, before we try to boil the ocean that is PyPI :)</p></blockquote></div><div apple-content-edited="true">As you can probably guess from my posts, I don’t think trying to replace Travis-CI is a good idea. What they do is *a lot* of work and maintenance and takes a lot of capacity, even if we restrict it to just Python projects.</div><div apple-content-edited="true"><br>-----------------<br>Donald Stufft<br>PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
</div>
<br></body></html>