Dealing with bugs that are only in trunk.

[Curtis Hovey-Canonical]

I think the number of open critical and high bugs is inflated. The
open critical bugs are an incentive to release soon, but many of the
critical bugs were really closed the moment trunk merged the fix.

We close bugs when we know we have delivered a fix to the affected
users. Our practice of targeting to milestones/releases is a little
misleading if we assume the bug was in the previous release. Some bugs
only affect users of trunk, such as developers and testers.

There are several bugs targeted to 1.17.0 that were introduced in
trunk and were fixed a few days later. I think these bugs are fix
released since developers and CI are no longer affected. I want to
close the bugs. It would then be easy to see which critical bugs we
want to release to users.

I have previously downgraded bugs to high when the fix hit trunk, or
if the fix was delivered in a stable point release. I don't like this
practice because it looks like critical importance was used
deceptively. Since we review all the open bugs to write release notes,
we are constantly re-reading bugs that don't affect anyone who will
get the release.

-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui