Hi, I have updated the section about Outdated Tickets on the Wiki. Does this capture the thoughts and the discussion we had on the reflector? https://wiki.iotivity.org/jira_how_to_use?&#outdated_tickets
thanks Christian On 27 Mar 2017, at 06:27, ??? (Uze Choi) <uzchoi at samsung.com<mailto:uzchoi at samsung.com>> wrote: Triage meeting across different time zone thru CC looks very challenging topic. Specially maintainers in India and PST zone are not easy to meeting simultaneously. Slack was proposed to communicate all together, even though which is against some company security policy. Let's check this tool is acceptable from each company by default or after additional internal process. BR, Uze Choi -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org<mailto:[email protected]> [mailto:iotivity-dev- bounces at lists.iotivity.org<mailto:bounces at lists.iotivity.org>] On Behalf Of Christian Gran Sent: Monday, March 27, 2017 4:23 AM To: Mats Wichmann; Gregg Reynolds; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] Jira cleanup Hi, sounds as if we are on the same page here. Tickets need to be looked at regularly. Current Jira has tickets going back to 2014 (last updated). thanks Christian On 26 Mar 2017, at 19:29, Mats Wichmann <mats at wichmann.us<mailto:mats at wichmann.us>> wrote: On 03/26/2017 01:21 AM, Christian Gran wrote: Hi, Having so many outdated tickets makes planning really difficult - you are right this is a management issue - and we have to manage our releases. We need to tell OCF and others when we have which releases and which features and tickets are in it. Now that reasoning just sounds silly: one of the most common reasons for liking Jira (and thus for "management" being willing to pay for it, over the multitude of free ticketing systems) is its reporting capability. Surely we can do a simple thing like extract the tickets tagged for a particular release without it being affected by whether there are other tickets not tagged for that release? I'd also like to add support for having regular triage. I know a meeting will be tricky to schedule with the timezones. The purpose of triage is why that term is chosen - get a quick look at things and decide what needs to happen right away, what can wait, how to categorize it, etc. It's really frustrating if you take the time to write up a bug and *nothing* happens with it; it should never be a long time before at least a first reaction takes place. _______________________________________________ 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/20170327/9eb43253/attachment.html>
