[Pharo-project] Closing unresolved issues
For example... Issue 5656: Large fonts make tools slow http://code.google.com/p/pharo/issues/detail?id=5656 This issue has not been resolved, but the issue was closed, leading to this experience... - I just upgraded a project to 2.0 - I notice that the UI is very slow - a simple Spec dialog window with a few text fields and buttons takes ~4 seconds to open - I check the issue tracker because I remember I reported the bug already, but I don't find it in the open issues - I waste time because I think it must be something else - I finally expand my search through the issues and find my report was closed as invalid I'm not saying that this is wrong, just that I don't understand and want to share another perspective and come to the best solution... What benefit are we getting from closing these that is significant enough to justify this kind of experience (I'm sure I'm not the only one). Cheers, Sean -- View this message in context: http://forum.world.st/Closing-unresolved-issues-tp4664420.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
+1 On 21 Jan 2013, at 17:35, "Sean P. DeNigris" <sean@clipperadams.com> wrote:
For example... Issue 5656: Large fonts make tools slow http://code.google.com/p/pharo/issues/detail?id=5656
This issue has not been resolved, but the issue was closed, leading to this experience... - I just upgraded a project to 2.0 - I notice that the UI is very slow - a simple Spec dialog window with a few text fields and buttons takes ~4 seconds to open - I check the issue tracker because I remember I reported the bug already, but I don't find it in the open issues - I waste time because I think it must be something else - I finally expand my search through the issues and find my report was closed as invalid
I'm not saying that this is wrong, just that I don't understand and want to share another perspective and come to the best solution... What benefit are we getting from closing these that is significant enough to justify this kind of experience (I'm sure I'm not the only one).
Cheers, Sean
Thanks for your feedback. Sean and I understand your frustration. The problem is what do we do if we have many bugs with nobody looking at them.
For example... Issue 5656: Large fonts make tools slow http://code.google.com/p/pharo/issues/detail?id=5656
This issue has not been resolved, but the issue was closed, leading to this experience... - I just upgraded a project to 2.0 - I notice that the UI is very slow - a simple Spec dialog window with a few text fields and buttons takes ~4 seconds to open - I check the issue tracker because I remember I reported the bug already, but I don't find it in the open issues - I waste time because I think it must be something else - I finally expand my search through the issues and find my report was closed as invalid
I'm not saying that this is wrong, just that I don't understand and want to share another perspective and come to the best solution... What benefit are we getting from closing these that is significant enough to justify this kind of experience (I'm sure I'm not the only one).
Cheers, Sean
-- View this message in context: http://forum.world.st/Closing-unresolved-issues-tp4664420.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Stéphane Ducasse wrote
The problem is what do we do if we have many bugs with nobody looking at them.
Maybe a good compromise would be a status like "Stale", where we can exclude them from searches if we want, but they are still being tracked? -- View this message in context: http://forum.world.st/Closing-unresolved-issues-tp4664420p4664618.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Jan 22, 2013, at 5:17 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
For example... Issue 5656: Large fonts make tools slow http://code.google.com/p/pharo/issues/detail?id=5656
This issue has not been resolved, but the issue was closed, leading to this experience... - I just upgraded a project to 2.0 - I notice that the UI is very slow - a simple Spec dialog window with a few text fields and buttons takes ~4 seconds to open - I check the issue tracker because I remember I reported the bug already, but I don't find it in the open issues - I waste time because I think it must be something else - I finally expand my search through the issues and find my report was closed as invalid
I'm not saying that this is wrong, just that I don't understand and want to share another perspective and come to the best solution... What benefit are we getting from closing these that is significant enough to justify this kind of experience (I'm sure I'm not the only one).
Yes, I was too fast closing this report⦠I will open it again. Marcus
participants (4)
-
Marcus Denker -
Sean P. DeNigris -
Stéphane Ducasse -
Sven Van Caekenberghe