Lennart Regebro wrote at 2004-4-30 22:21 +0200:
>Dieter Maurer wrote:
>> 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:
>> 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. :)
You should not close true bug reports.
Doing so is (in my view) a bad approach to quality.
>> 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.
In my view this should only happen for reports that are not bugs.
Reports (of some quality) about true bugs (or unanticipated behaviour)
are valuable even when nobody plans to actually fix them.
>> 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
You risk to get less bug reports in the collector...
Filing a (good) bug report takes quite a bit of time.
When you have gotten rejections for several bug reports
(that took you quite a bit of time) you will start thinking
whether the next bug report is worth the effort.
I do not think this is what the community should wish for...
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -