I second that. Don?t close issue without a proper reason. It?s very detrimental to community involvement. See it from their point of view: Not only did their issue get ignored for oh so long, but it then just got closed with no good reason why, besides ?we were too lazy to look at it? (I?m not saying you?re lazy ? just that that can be how it?ll come across).
/Morten From: C.J. Collier<mailto:[email protected]> Sent: Friday, March 24, 2017 3:27 PM To: Christian Gran<mailto:gran at lynxtechnology.com> Cc: IoTivity Developer List<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Jira cleanup Hi folks! For the AllJoyn Open Source Project, we meet weekly to triage bugs. I recommend that we schedule a call to go through the issues rather than closing them potentially without review. We can assume that an issue well be closed as stalled if a decision is not made otherwise if that helps to clear our the backlog. I'm afraid we'll lose a lot of sold community feedback if we close issues just because they are old. Just my 2? C.J. Sent from my PDP-11 On Mar 10, 2017 00:59, "Christian Gran" <gran at lynxtechnology.com<mailto:gran at lynxtechnology.com>> wrote: Hi, there are currently 141 issues in Jira, that are in open state and have not been updated for more then 6 month now. The plan is to clean up Jira and close outdated tickets by end of March. If you see a ticket, that you still want to keep - please just add a comment to it. This will update the ?updated date? field and it will no longer be part of the filtered tickets. For the list of tickets, please use this Jira filter: status in (Open, "In Progress", Reopened, Assigned, "To Do", "In Review") AND updated <= -180d or just this link https://jira.iotivity.org/issues/?jql=status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20Assigned%2C%20%22To%20Do%22%2C%20%22In%20Review%22)%20AND%20updated%20%3C%3D%20-180d<https://jira.iotivity.org/issues/?jql=status%20in%20(Open,%20%22In%20Progress%22,%20Reopened,%20Assigned,%20%22To%20Do%22,%20%22In%20Review%22)%20AND%20updated%20%3C=%20-180d> Please feel free to comment, or if you have some more input how we can make sure that we only keep issues in Jira we are actually working on?. thanks Christian _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170324/a0b49a39/attachment.html>
