Bugzappers EOL process and abrt bug reporters being flagged with needinfo before bugs are closed?

Michael Schwendt mschwendt at gmail.com
Mon Dec 6 15:50:41 UTC 2010


On Mon, 06 Dec 2010 10:08:35 -0500, James wrote:

> The alternative is silently
> closing EOL'd bugs.  I don't think silently closing bugs works well with
> the principle of least surprise.

The alternative is to communicate with the reporter much earlier.
1) When there is a stable update of the package the bug has been
reported about. 2) When there is a new dist release, even if it doesn't
contain a version upgrade of the software the bug has been reported
about. 3) When the package maintainer has not responded in any way
after N months.

Case 1) may be especially helpful for products where version upgrades
contain a large number of changes (including code redesign), which
make it difficult or impossible to find out whether a bug has been
fixed.

The earlier automated (!) NEEDINFO request could also be used to point at
a bug reporting HOWTO once more. And to repeat the request for a comment
on the reproducibility and how to reproduce a problem.


More information about the test mailing list