Closing valid bugs which were merely assigned to the wrong package
isn't acceptable (though admitedly, it *is* better than just ignoring
them entirely.)
Closing a valid bug without fixing is generally wrong, like in this
case, whether there is enough manpower to treat it or not.
And if you have
I want to hear your opinion about the following question: If you think
a bug does not belong to your package, do you think it is your duty as a
maintainer to reassign to bug to the package it belongs to or do you
think just closing the bug is fine?
Closing a report merely because it is assigned
On Fri, 18 Apr 2008, Andrei Popescu wrote:
If anybody would confirm that this problem might belong to module-init-tools
I would volunteer to take over the job of proper reassignment - but I
just don't know exactly and "my experts in questions like this" just
refuse proper communication.
See #4
On Fri, Apr 18, 2008 at 02:40:47PM +0200, Andreas Tille wrote:
[...]
> On Tue, 8 Apr 2008 I filed #474964 against linux-2.6:
> Loads pcspkr and others even if explicitely excluded in modprobe.conf
[...]
> If anybody would confirm that this problem might belong to module-init-tools
> I would vol
On Fri, 18 Apr 2008, Andreas Tille wrote:
> I want to hear your opinion about the following question: If you
> think a bug does not belong to your package, do you think it is your
> duty as a maintainer to reassign to bug to the package it belongs to
> or do you think just closing the bug is fine?
Hi,
I want to hear your opinion about the following question: If you think
a bug does not belong to your package, do you think it is your duty as a
maintainer to reassign to bug to the package it belongs to or do you
think just closing the bug is fine?
My understanding of handling bugs is that
6 matches
Mail list logo
