check-newsbugs.py does not know about version specific tasks

Bug #586430 reported by Robert Collins on 2010-05-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Wishlist
Unassigned

Bug Description

Running check-newsbugs.py when doing 2.1.2 reporting the following:
Bug 583941 was mentioned in NEWS but is not marked fix released:
Launchpad title: program crashes with "bzr: ERROR: socket.error: (4, 'Interrupted system call')"
NEWS summary:
* Do not register a SIGWINCH signal handler, instead just poll for the
  terminal width as needed. This avoids the "Interrupted System Call"
  problems that occur on POSIX with all currently released versions of
  Python.
  (Andrew Bennetts, #583941)

Bug 174625 was mentioned in NEWS but is not marked fix released:
Launchpad title: Performance regression with pack format in missing
NEWS summary:
* ``bzr missing`` uses the new ``Graph.find_unique_ancestors`` and
  ``Graph.find_differences`` to determine missing revisions without having
  to search the whole ancestry. (John Arbash Meinel, #174625)
...
and more

At that time, the first bug was 'fix released' in 2.1 - so should not have been reported.
The second bug is 'fix released' in bzr but open in debbugs (which is a bug I think), but still - in both cases NEWS is correct in listing the bug, and check-newsbugs incorrect in complaining.
With the amount of false positives, check-newsbugs took longer to evaluate than just opening all the bugs for 2.1.2 directly, a real disincentive :(.

summary: - check-newsbugs,py does not know about version specific tasks
+ check-newsbugs.py does not know about version specific tasks
Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers