+1 to a triage meeting. The core issue here in my opinion is the lack of a weekly triage meeting. The weekly status check in AllJoyn is what prevented bugs from falling between the cracks or becoming stale (e.g., fixed as a side effect of fixing some other bug, etc.)
From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of C.J. Collier Sent: Friday, March 24, 2017 3:27 PM To: Christian Gran <gran at lynxtechnology.com> Cc: IoTivity Developer List <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/20170326/5d9df3d2/attachment.html>
