Bug#24067: Is it ok to close a bug without fixing it?
Hi,
>>"Darren" == Darren O Benham <gecko@debian.org> writes:
Darren> Actually, I think developer disputes are handled by the technical
Darren> committee.
Fine. Forward it to them, then. The policy mailing list is
there to take care of *non-controversial* technical issues, and this
happens to be neither. We work by near consensus.
If this were indeed a policy issue, then this should be a
proposal. It is not. The bug filer even said this is not meant to be
a proposal. As such, I think this has no place here.
This report is merely cluttering up the bug page for
debian-policy, which is used to track the status of discussions on
policy itself.
Darren> However, how and when to close bugs is a behavioral thing
Darren> governing how a developer is supposed to behave with the Debian
Darren> organization, would that not be policy?
Nope. This is a technical policy, or supposed to be. We decided
that the bug closing conventions better belong in something like
developers-referece(along with admonitons about the mailing list and
everything), and a wishlist bug with suggested wording has been filed
against that package [#39519: Recommended Bug closure practice].
manoj
--
You can write a small letter to Grandma in the filename. Forbes
Burkowski, CS, University of Washington
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: