Casey Duncan wrote at 2004-4-29 22:19 -0400:
I'm happy to report a successful bug day with a final tally of almost 40 issues closed. The specific issues we squashed were:
#28,#181,#321,#340,#349,#439,#444,#495,#511,#532,#540,#543, #544,#545,#546,#553,#562,#574,#584,#602,#637,#644,#654,#658,#666, #678,#724,#800,#810,#811,#875,#1003,#1042,#1050,#1148,#1227,#1298, #1300.
However, you closed (at least one) bug reports without resolving the the issue.
Make no mistake about this. Had I not spend yesterday on a plane, there would have been many issues closed without resolving it.
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. :)
I do not think this is good practice...
Bug reports should remain open until they are either fixed
or can no longer occur.
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.
They should not be closed just because you do not plan to fix them in the near future...
True. But if they are not planned to be fixed at all, then they should be closed.
_______________________________________________
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 )
