I think Gregg has a point. There are bug reports on jira which potentially a big security threat to systems running Iotivity.
Which only Iotivity devs have knowledge to judge whether it is a severe bug or just something minor and could be ignored. From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Gregg Reynolds Sent: Saturday, March 25, 2017 6:32 AM To: Christian Gran Cc: iotivity-dev at lists.iotivity.org Subject: Re: [dev] Jira cleanup On Mar 24, 2017 4:01 AM, "Christian Gran" <gran at lynxtechnology.com> wrote: Hi, thanks Dave and George, this is very good input. In my oinion the minimal thing we should do with tickets we want to keep is: 1) agree on someone who owns the ticket (assign) 2) check in 3 month if the ticket has been worked on (may be split into other tickets, resolved as outdated, ?) For a ticket where we are unable to find someone who can own it I would suggest to close it - it does not make sense to use Jira as a white board to collect tickets that no one can work on. How does this sound? respectfully, it sounds preposterous to me. this is just not how things work. suppose i find a hideous massive security-related bug, but nobody has time to work on it. by your logic we just just close it. this is an open source project, not a corporate project. you cannot make the kind of demands on it that you might be able to make if you are in charge of everything. jira tix should *never* be closed, only resolved. g -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170328/50efbde2/attachment.html>
