[Issue tracker] what about old issues?
Hi, we have 666 open issues on the issue tracker. It seems that older issues do not get looked at much⦠the question is what to do: the more open issues we have, the less likely they will ever be looked at. I would like to -> automatically put them on âclosed, timeoutâ -> send a mail to the original submitter AND pharo-dev This way people can just re-open important issues, but those issues where the submitter does not care and nobody else, either, would be closed after one year⦠(This would e.g. include lots of issues that got fixed in the meantime⦠or non-important âit would be niceâ issues, or those where nobody (eve the submitter) understands what this is about anymoreâ¦) Marcus
2015-04-28 17:44 GMT+02:00 Marcus Denker <marcus.denker@inria.fr>:
Hi,
we have 666 open issues on the issue tracker.
It seems that older issues do not get looked at much⦠the question is what to do: the more open issues we have, the less likely they will ever be looked at.
I would like to
-> automatically put them on âclosed, timeoutâ -> send a mail to the original submitter AND pharo-dev
+1
This way people can just re-open important issues, but those issues where the submitter does not care and nobody else, either, would be closed after one year⦠(This would e.g. include lots of issues that got fixed in the meantime⦠or non-important âit would be niceâ issues, or those where nobody (eve the submitter) understands what this is about anymoreâ¦)
Marcus
666 open issues
The tracker is telling us that old issues are evil. :)
-> automatically put them on âclosed, timeoutâ
-> send a mail to the original submitter AND pharo-dev
Maybe in the opposite order? After a period [year] send mail and if no response within a week or two then close it.
On 28 Apr 2015, at 18:19, Peter Uhnák <i.uhnak@gmail.com> wrote:
666 open issues The tracker is telling us that old issues are evil. :)
:-)
-> automatically put them on âclosed, timeoutâ -> send a mail to the original submitter AND pharo-dev Maybe in the opposite order? After a period [year] send mail and if no response within a week or two then close it.
it would be easier to automateâ¦. Marcus
On 28 Apr 2015, at 19:55, Marcus Denker <marcus.denker@inria.fr> wrote:
On 28 Apr 2015, at 18:19, Peter Uhnák <i.uhnak@gmail.com> wrote:
666 open issues The tracker is telling us that old issues are evil. :)
:-)
-> automatically put them on âclosed, timeoutâ -> send a mail to the original submitter AND pharo-dev Maybe in the opposite order? After a period [year] send mail and if no response within a week or two then close it.
it would be easier to automateâ¦.
Marcus
Yes, it should be automated (saving people's time is very important). And yes, issue that are too old for anyone to care about should be deactivated.
On a related topic, I'm not sure if we want every Fogbugz comment to come to the list, but can Fogbugz be configured to post just the Issue Open comment to this mail list. This should help us perform bug-report QA up front when the reporter has details to hand. If required reproducability details are not forthcoming, then we close the issue early. cheers -ben On Wed, Apr 29, 2015 at 2:17 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
On 28 Apr 2015, at 19:55, Marcus Denker <marcus.denker@inria.fr> wrote:
On 28 Apr 2015, at 18:19, Peter Uhnák <i.uhnak@gmail.com> wrote:
666 open issues The tracker is telling us that old issues are evil. :)
:-)
-> automatically put them on âclosed, timeoutâ -> send a mail to the original submitter AND pharo-dev Maybe in the opposite order? After a period [year] send mail and if no response within a week or two then close it.
it would be easier to automateâ¦.
Marcus
Yes, it should be automated (saving people's time is very important). And yes, issue that are too old for anyone to care about should be deactivated.
On Wed, Apr 29, 2015 at 1:40 AM, Ben Coman <btc@openinworld.com> wrote:
every Fogbugz comment to come to the list
There is already separate pharo-issues mailing list ( http://forum.world.st/Pharo-Issue-Tracker-f3456798.html ) so no need to duplicate it. However it would make sense to send periodical (daily or weekly) updates - something that was proposed previously â http://forum.world.st/More-people-needed-to-review-issues-td4800916.html#a48... So maybe it could be incorporated into that. # Issues to be closed due to inactivity: - issueX - issueY etc (plus of course automted mail to the issue opener/assigned person). I don't know how friendly FogzBugz is with automating such mails. Peter
participants (5)
-
Ben Coman -
Marcus Denker -
Nicolai Hess -
Peter Uhnák -
Sven Van Caekenberghe