Bug#23355: PROPOSED] On closing of bugs
> On Mon, 31 May 1999, Julian Gilbey wrote:
>
> > Now that we have a "fixed" priority in the developers-reference (this
> > is not in policy itself), can this proposal be closed?
>
> Well, what I would like to see is a general policy about bugs, covering
> all aspects of bug reporting, forwarding, severitying and closing. Who is
> allowed to do that, and when. For example, how many times are a submitter
> allowed to reopen a bug (I would say that only once), or how do we decide
> about a bug being normal or wishlist (current practice says package
> maintainer has the last word about this).
No, we just need some common sense, common courtesy (which none of us
seem to be so good at ;), some good relaxation techniques and some
good interpersonal skills.
Just being able to throw policy against a bug-submitter doesn't
prevent something from being a bug. And just submitting bugs against
a maintainer doesn't make it one.
Maybe there should be something in policy about disputes, but I would
guess that if there is a dispute, it would usually mean that there is
something akin to a bug present. And if the maintainer doesn't want
to "fix" it, he should at least not close the report, leaving the
reasoning present in the report.
Julian
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Reply to: