Re: spam closes Debian bugs!
On Mon, 15 Mar 2004, Enrico Zini wrote:
> Package A has a bug that's caused by a bug in library B. Library B gets
> a new upload before the bug is reassigned. A user of package A could
> notice that and close the bug leveraging the work of the busy or
> vacationed maintainer of A (although retitling as a request of versioned
> depend would be better). In general, users can be the best to discover
> that a bug is not so anymore.
Sure - they should foreward this information to the BTS and perhaps they
could tag it "fixed". But they should not *close* the bug.
> People doing random scans of the BTS archive could do investigation and
> discover that an old bug, maybe dealing with changing environmental
> issues, is not valid anymore, and thus close them.
IHMO, closing a bug should be done by the maintainer or the QA team in
case of MIA maintainers but not by random users.