When to close bugs on old package versions
When a bug applies to an old version of a package (say, a version only in
Potato) when should that bug be closed? If it's not security or
life-threatening to the package, it will pretty much never get fixed in
Potato, but it's still a bug. Perhaps it should be tagged wontfix and be
done with it? Since it's not been fixed, it shouldn't be closed, but it
still looks unpleasant.
And what about when, for instance, potato is replaced as the stable distro
by Woody? Should the bug be closed then because it's no longer relevant?
Perhaps it's closed automatically because it's tagged 'Potato', I don't
know.
Anyway, just trying to think my way through a few issues with the BTS and
the hows, whys, and wheretofores of bug handling when there are multiple
simultaneous versions of a package for bugs to be tracked on.
--
-----------------------------------------------------------------------
#include <disclaimer.h>
Matthew Palmer
mjp16@ieee.uow.edu.au
--
To UNSUBSCRIBE, email to debian-mentors-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: