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.
https://github.com/dreid/treq/blob/master/.travis.yml shows how I do this with travis-ci. -David On Thu, Jan 17, 2013 at 12:15 PM, Glyph <gl...@twistedmatrix.com> wrote: > > On Jan 17, 2013, at 9:19 AM, exar...@twistedmatrix.com wrote: > > (although testing during the /pre/-release period would have saved > everyone some > trouble :). > > > This bears repeating! Not to harass you, Angelo - dealing with a > regression in Twisted that breaks your app is punishment enough :) - but to > remind everyone that this is exactly why we have the pre-release testing > period. > > When you get the 13.0 release announcement, please remember that you only > have a week! All you need to do is to run your respective test suite and > send a short email saying if you found any issues. (Filing a ticket would > be nice, but if that's too much work, don't worry about it: for pre-release > regressions, we'll file tickets and work on patches for you.) > > -glyph > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > >
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
