Hi Thomas, do you have any further take on this? If there's no strong objection I'd like to move forward.
Cheers On 3 November 2016 at 21:17, Free Ekanayaka <fr...@debian.org> wrote: > Hi Thomas, > > On 3 November 2016 at 20:25, Thomas Goirand <z...@debian.org> wrote: > >> On 11/03/2016 12:08 PM, Free Ekanayaka wrote: >> > Package: python-testtools >> > Version: 1.8.0-4 >> > Severity: normal >> > >> > The 1.8.0 release is over a year old. In the meantime several bug >> > fixes and improvements have landed upstream and are available in >> > the 2.2.0 release, so we should upgrade the Debian package. >> > >> > If you wish, I volunteer for co-maintainership or even simply an >> > ad-hoc NMU. >> >> I'm not sure if it is such a good idea to upgrade testtools just before >> the freeze of Stretch. Maybe we'd better upload it to Experimental? >> > > As mentioned, the 2.2.0 release is definitely an improvement over the > 1.8.0, with bug fixes even. For a stable release like Stretch, I would > rather prefer to see 2.2.0 in it than 1.8.0. > > For example unit tests for 2.2.0 are fully green on Debian/sid, both on > Python 2 and Python 3, while unit tests for 1.8.0 have several breakages. > > See these links to see the bugs that have been address in over a year: > > https://launchpad.net/testtools/+milestone/1.9.0 > https://launchpad.net/testtools/trunk/1.8.1 > https://launchpad.net/testtools/trunk/2.0.0 > https://launchpad.net/testtools/trunk/2.1.0 > https://github.com/testing-cabal/testtools/issues?q=is%3Aissue+is%3Aclosed > > Free >
