On Mon, May 31, 1999 at 01:56:07PM -0700, Joey Hess wrote: > Santiago Vila wrote: > > 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). > > Well I wouldn't like to see this. In general, we haven't had a problem with > this, except for a ver very rare cases of arguments or abuse. I don't think > those cases warrent putting every developer into a straightjacket.
How about a convention instead :-) For instance, NMU's cannot close bugs (only mark them fixed), however the only reason I've heard is that the fix may be lost if the maintainer then does a release. If the NM and the maintainer are in contact then this is fine - and so we could close the bug. Guidelines if you like. Cheers Adrian email: [EMAIL PROTECTED], http://www.poboxes.com/adrian.bridgett Windows NT - Unix in beta-testing. PGP key available on public key servers Avoid tiresome goat sacrifices -=- use Debian Linux http://www.debian.org
