Ticket closing policy
Hi Mark, hi all, I noticed you did a lot of cleaning in the bug trackers, thank you for helping there, this is sorely needed. However, I noticed quite a few tickets were closed as wontfix even though they are valid. I understand the concern of getting many languishing tickets, but one should not close valid tickets either. Also, in my experience, issues specific to win32 should not be closed because they work on Linux - I remember the fastputmask issue was still there not so long ago (but could not understand what was going on, unfortunately). cheers, David
On Fri, Mar 25, 2011 at 4:22 AM, David
Hi Mark, hi all,
I noticed you did a lot of cleaning in the bug trackers, thank you for helping there, this is sorely needed.
However, I noticed quite a few tickets were closed as wontfix even though they are valid.
I checked all the wontfix tickets and reopened two, but I agreed with the others. Never closing tickets if they are valid (even though it's clear they will not be resolved anymore) is not a useful policy either IMHO. For example, the bug report of a build issue of numpy 1.0.1 on IRIX could still be valid, but no more info or help on this ticket for 3 years. So close as wontfix. If a new IRIX user comes along and this is still an issue, it can be reopened or a new ticket can be opened. Cheers, Ralf
I understand the concern of getting many languishing tickets, but one should not close valid tickets either. Also, in my experience, issues specific to win32 should not be closed because they work on Linux - I remember the fastputmask issue was still there not so long ago (but could not understand what was going on, unfortunately).
cheers,
David
On Thu, Mar 24, 2011 at 8:22 PM, David
Hi Mark, hi all,
I noticed you did a lot of cleaning in the bug trackers, thank you for helping there, this is sorely needed.
However, I noticed quite a few tickets were closed as wontfix even though they are valid. I understand the concern of getting many languishing tickets, but one should not close valid tickets either. Also, in my experience, issues specific to win32 should not be closed because they work on Linux - I remember the fastputmask issue was still there not so long ago (but could not understand what was going on, unfortunately).
I understand your concern, but I think since dealing with bug reports requires subjective judgement calls, it's going to be a bit messy. That's why the bug tracker timeline is there to let people see what changes have been made and peer review those choices. In the fastputmask case, it was about the test suite crashing on win32 as well as a memory leak on Linux. I commented about testing the latter, but could have also added a justification for the former that no win32 test suite crash reports were coming in during the beta testing. Regardless, please add to the discussion on any bugs I've modified where you believe I've erred, this is a collaborative effort! Cheers, Mark
participants (3)
-
David
-
Mark Wiebe
-
Ralf Gommers