[Issue Tracker] Call for CleanUp of the issue tracker
Hello, There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦). A lot of those issues are very old. A lot are in a bad shape: -> not reproducible -> *completely* unclear what action could lead to solve the issue -> outdated (e.g. small improvements submitted ages ago, but even the author does not care to submit a new version for Pharo4) I think we should be more radical in closing issues. If someone submits something but can not even answer a simple question in 2 months â> this is the same as âI donât careâ. So *PLEASE*: -> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action? Marcus
Yes but, 2014-09-17 11:25 GMT+02:00 Marcus Denker <marcus.denker@inria.fr>:
Hello,
There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦).
A lot of those issues are very old. A lot are in a bad shape:
-> not reproducible -> *completely* unclear what action could lead to solve the issue -> outdated (e.g. small improvements submitted ages ago, but even the author does not care to submit a new version for Pharo4)
I think we should be more radical in closing issues. If someone submits something but can not even answer a simple question in 2 months â> this is the same as âI donât careâ.
2 months are to short. 4 or maybe 6. There are open issues without any action on our part - for months. And that does not mean "we don't care". If someone reports an issues and don't have the time to react on comments/questions for a couple of months, I understand that. nicolai
So *PLEASE*:
-> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action?
+1
Marcus
On 17 Sep 2014, at 13:02, Nicolai Hess <nicolaihess@web.de> wrote:
Yes but,
2014-09-17 11:25 GMT+02:00 Marcus Denker <marcus.denker@inria.fr>: Hello,
There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦).
A lot of those issues are very old. A lot are in a bad shape:
-> not reproducible -> *completely* unclear what action could lead to solve the issue -> outdated (e.g. small improvements submitted ages ago, but even the author does not care to submit a new version for Pharo4)
I think we should be more radical in closing issues. If someone submits something but can not even answer a simple question in 2 months â> this is the same as âI donât careâ.
2 months are to short. 4 or maybe 6. Yes, you are right 6 months is good.
The idea is that the issue will be closed, but with a mail to the âownerâ of the issue so that he/she can decide to re-open⦠and âwill work on that laterâ would be a valid answer.
There are open issues without any action on our part - for months. And that does not mean "we don't care". If someone reports an issues and don't have the time to react on comments/questions for a couple of months, I understand that.
nicolai
So *PLEASE*:
-> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action?
+1
Marcus
On Sat, Sep 20, 2014 at 12:28 PM, Ben Coman <btc@openinworld.com> wrote:
I have two tickets open on Penelope... https://pharo.fogbugz.com/default.asp?11550 https://pharo.fogbugz.com/default.asp?11551
I'd be happy to give them a go myself if I had access to the code and be able to test it. cheers -ben
can anyone help Ben? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill
On 22 Sep 2014, at 18:23, Damien Cassou <damien.cassou@gmail.com> wrote:
On Sat, Sep 20, 2014 at 12:28 PM, Ben Coman <btc@openinworld.com> wrote:
I have two tickets open on Penelope... https://pharo.fogbugz.com/default.asp?11550 https://pharo.fogbugz.com/default.asp?11551
I'd be happy to give them a go myself if I had access to the code and be able to test it. cheers -ben
can anyone help Ben?
I would be interesting to have information about this⦠I do not know it, either. Marcus
Nobody knows? This thread is frightening... Le 20 sept. 2014 12:29, "Ben Coman" <btc@openinworld.com> a écrit :
I have two tickets open on Penelope... https://pharo.fogbugz.com/default.asp?11550 https://pharo.fogbugz.com/default.asp?11551
I'd be happy to give them a go myself if I had access to the code and be able to test it. cheers -ben
Marcus Denker wrote:
On 17 Sep 2014, at 13:02, Nicolai Hess <nicolaihess@web.de> wrote:
Yes but,
2014-09-17 11:25 GMT+02:00 Marcus Denker <marcus.denker@inria.fr>:
Hello,
There are right now 675 open issues. (we managed to close 63 just the last 7 days...).
A lot of those issues are very old. A lot are in a bad shape:
-> not reproducible -> *completely* unclear what action could lead to solve the issue -> outdated (e.g. small improvements submitted ages ago, but even the author does not care to submit a new version for Pharo4)
I think we should be more radical in closing issues. If someone submits something but can not even answer a simple question in 2 months --> this is the same as "I don't care".
2 months are to short. 4 or maybe 6.
Yes, you are right 6 months is good.
The idea is that the issue will be closed, but with a mail to the "owner" of the issue so that he/she can decide to re-open... and "will work on that later" would be a valid answer.
There are open issues without any action on our part - for months. And that does not mean "we don't care". If someone reports an issues and don't have the time to react on comments/questions for a couple of months, I understand that.
nicolai
So *PLEASE*:
-> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action?
+1
Marcus
On 29 Sep 2014, at 07:53, Damien Cassou <damien.cassou@gmail.com> wrote:
Nobody knows? This thread is frightening...
The bugs.pharo.org related issue related to the fact that it never ever updated the issues shown is open since 1 week after it was set up, or something like that. Marcus
Le 20 sept. 2014 12:29, "Ben Coman" <btc@openinworld.com> a écrit :
I have two tickets open on Penelope... https://pharo.fogbugz.com/default.asp?11550 https://pharo.fogbugz.com/default.asp?11551
I'd be happy to give them a go myself if I had access to the code and be able to test it. cheers -ben
Marcus Denker wrote:
On 17 Sep 2014, at 13:02, Nicolai Hess <nicolaihess@web.de> wrote:
Yes but,
2014-09-17 11:25 GMT+02:00 Marcus Denker <marcus.denker@inria.fr>: Hello,
There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦).
A lot of those issues are very old. A lot are in a bad shape:
-> not reproducible -> *completely* unclear what action could lead to solve the issue -> outdated (e.g. small improvements submitted ages ago, but even the author does not care to submit a new version for Pharo4)
I think we should be more radical in closing issues. If someone submits something but can not even answer a simple question in 2 months â> this is the same as âI donât careâ.
2 months are to short. 4 or maybe 6. Yes, you are right 6 months is good.
The idea is that the issue will be closed, but with a mail to the âownerâ of the issue so that he/she can decide to re-open⦠and âwill work on that laterâ would be a valid answer.
There are open issues without any action on our part - for months. And that does not mean "we don't care". If someone reports an issues and don't have the time to react on comments/questions for a couple of months, I understand that.
nicolai
So *PLEASE*:
-> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action?
+1
Marcus
Nicolai Hess wrote
There are open issues without any action on our part - for months. And that does not mean "we don't care"
Please give issues which are closed simply because they are "stale" the "postponed" status so they can be more easily found later (per http://forum.world.st/Issue-Tracker-input-of-submitters-bug-fixers-needed-tp...) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-Tracker-Call-for-CleanUp-of-the-issue-tracker-tp... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 21 Sep 2014, at 17:09, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
There are open issues without any action on our part - for months. And that does not mean "we don't care"
Please give issues which are closed simply because they are "stale" the "postponed" status so they can be more easily found later (per http://forum.world.st/Issue-Tracker-input-of-submitters-bug-fixers-needed-tp...)
Maybe we should add a special close status for those⦠But for me it is important that they are âclosed* in the sense that they do not take any brain power when looking at the issue tracker. If the original submitter does not care after e.g. 1 year, I want to have the OK officially to be allowed to not care, either. Marcus
Marcus Denker-4 wrote
But for me it is important that they are âclosed*
I understand. It seems Closed + special status serves both needs. I had proposed "stale" before, but it seemed that existing "postponed" was close enough last time we discussed. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-Tracker-Call-for-CleanUp-of-the-issue-tracker-tp... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 22 Sep 2014, at 15:00, Sean P. DeNigris <sean@clipperadams.com> wrote:
Marcus Denker-4 wrote
But for me it is important that they are âclosed*
I understand. It seems Closed + special status serves both needs. I had proposed "stale" before, but it seemed that existing "postponed" was close enough last time we discussed.
I will add a "Closed (stale)â status (sometimes when I find time later the week) Marcus
On 17 Sep 2014, at 11:25, Marcus Denker <marcus.denker@inria.fr> wrote:
Hello,
There are right now 675 open issues. (we managed to close 63 just the last 7 daysâ¦).
Open issues are down to 658. Especially old issues need help! It *so* much less work for someone who was involved (maybe the original submitter?) in an issue in the past than someone who looks at it from scratch! A *lot* of old issues can be closed just by trying to re-create the bug and then seeing that it has been fixed ages ago,
-> check all the issue that *you* submitted. Are they still relevant? Is there enough information for anyone to do anything? -> check all the issues you where involved with in discussions. It is much easier for you than for me to understand what the conclusion of the discussion is. -> help checking *old* entries. Is is still relevant? What is the next action?
Especially looking at your own issues, this is *very* needed. If an issue is open for 2 years, maybe the description is not well written? So ask yourself; Has the issue really enough information for *someone else* to act? (an issue tracker is not your personal TODO list!) Marcus
participants (5)
-
Ben Coman -
Damien Cassou -
Marcus Denker -
Nicolai Hess -
Sean P. DeNigris