Bug#843037: python-testtools: New upstream 2.2.0 available

[Free Ekanayaka]

On Mon, 7 Nov 2016 10:49:58 +0100, Thomas Goirand wrote:
> Hi,
>
> I do have a strong objection.
>
> The deadline for library transition was today, and therefore, it is
> strongly objected by the release team that we do not upgrade major versions.
>
> It is also my view that this shouldn't happen without testing all the
> reverse (build-)dependencies of python-testtools.
>
> So, unless you can show the build log for all nearly 100 reverse build
> dependencies, and show that nothing fails, then I am strongly against
> upgrading python-testtools at this point in time in the release cycle.

Okay, I've prepared an upload to experimental instead:

git://anonscm.debian.org/collab-maint/deb-python-testtools.git

I'll upload it there if it's fine for you. Changelog entry:

python-testtools (2.2.0-1.1) experimental; urgency=medium

  * Non-maintainer upload
  * New upstream release (Closes: #843037)
  * Fix debian/watch to match the new upstream tagging
scheme (in place since 0.9.23)
  * Re-enable running unit tests at build time, since they
are fixed
  * Drop fix-test-run.py.patch
  * Add build dependency on testscenarios
  * Bump Standards-Version to 3.9.8

 -- Free Ekanayaka   Sat, 12 Nov 2016 13:27:12 +

Bug#843037: [PKG-Openstack-devel] Bug#843037: python-testtools: New upstream 2.2.0 available

[Thomas Goirand]

On 11/07/2016 10:14 AM, Free Ekanayaka wrote:
> Hi Thomas,
> 
> do you have any further take on this? If there's no strong objection I'd
> like to move forward.
> 
> Cheers

Hi,

I do have a strong objection.

The deadline for library transition was today, and therefore, it is
strongly objected by the release team that we do not upgrade major versions.

It is also my view that this shouldn't happen without testing all the
reverse (build-)dependencies of python-testtools.

So, unless you can show the build log for all nearly 100 reverse build
dependencies, and show that nothing fails, then I am strongly against
upgrading python-testtools at this point in time in the release cycle.

Cheers,

Thomas Goirand (zigo)

Bug#843037: python-testtools: New upstream 2.2.0 available

[Free Ekanayaka]

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  wrote:

> Hi Thomas,
>
> On 3 November 2016 at 20:25, Thomas Goirand  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
>

Bug#843037: [PKG-Openstack-devel] Bug#843037: python-testtools: New upstream 2.2.0 available

[Thomas Goirand]

On 11/03/2016 09:17 PM, Free Ekanayaka wrote:
> Hi Thomas,
> 
> On 3 November 2016 at 20:25, Thomas Goirand  > 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.

If following the semantic versioning, 2.x means incompat with 1.x, so it
doesn't feel right so close from Stretch freeze. If it was bugfix only,
then I'd be more confident, but that's not the case. Myself alone
maintain 88 reverse build-dependencies. Are you sure none will break?
Upgrading to 1.8.1 seems more reasonable to me.

> 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.

Of testtools itself? Isn't its reverse build-depends more important?

Cheers,

Thomas Goirand (zigo)

Bug#843037: python-testtools: New upstream 2.2.0 available

[Free Ekanayaka]

Hi Thomas,

On 3 November 2016 at 20:25, Thomas Goirand  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

Bug#843037: python-testtools: New upstream 2.2.0 available

[Thomas Goirand]

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?

Your thoughts?
Cheers,

Thomas Goirand (zigo)

Bug#843037: python-testtools: New upstream 2.2.0 available

[Free Ekanayaka]

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.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.4.0-45-lowlatency (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python-testtools depends on:
ii  python-extras 0.0.3-3
ii  python-linecache2 1.0.0-3
ii  python-mimeparse  0.1.4-1
ii  python-pbr1.10.0-1
ii  python-pkg-resources  28.0.0-1
ii  python-traceback2 1.4.0-4
ii  python-unittest2  1.1.0-6.1
pn  python:any

Versions of packages python-testtools recommends:
ii  python-fixtures  3.0.0-2

Versions of packages python-testtools suggests:
pn  python-testtools-doc  
pn  python-twisted

-- no debconf information