<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 17, 2013, at 12:57 PM, David Reid <<a href="mailto:dreid@dreid.org">dreid@dreid.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Honestly, if you have comprehensive automated testing and plan to upgrade Twisted regularly or to try and support the latest release it is worth the effort to setup testing against Twisted trunk.<div><br></div>
<div><a href="https://github.com/dreid/treq/blob/master/.travis.yml">https://github.com/dreid/treq/blob/master/.travis.yml</a> shows how I do this with travis-ci.<br></div></div></blockquote><br></div><div>Thanks for the pointer, David. I will disseminate this more widely.</div><div><br></div><div>It's also important for the Twisted team to find out about failures though, so it's still important to _look_ at your travis-ci build results in the pre-release week to make sure that everything is still working, and let us know if it isn't.</div><div><br></div><div>It would be great if we could automate that, too; would it be possible to set up a page that just has at-a-glance build results for 3rd-party projects against twisted trunk?</div><br><div>-glyph</div><div><br></div></body></html>