There are many bugs with ambigous descriptions, or posted anonymously, or things that are rather like support questions than bugs. If I see them I close them. Hard and brutal. :)
This worries me. I think we need a better documented set of circumstances that are used for rejecting or closing bugs. It feels inconsistent right now, and the above kind of attitude, which keeping the number of open issues in the tracker to a minimum, isn't really helping to produce a better quality piece of software.
...and that is our aim here, right?
If the bug report is understandable, and repetable and indeed a bug, and not a misunderstanding, and the community thinks it should be fixed, then yes. But there are many instances where bugs should be closed without anything being changed at all.
Closed is wrong here, we need a "won't fix" state...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
