On Mar 25, 2017 2:04 AM, "Christian Gran" <gran at lynxtechnology.com> wrote:
Hi, we are talking here about two different things - that somehow got mixed up: 1) get a clean state: Looking at Jira today twe have more than 100 tickets that have not been looked at for more then 6 month. why is that a problem? why 6 months? why not 3, or 9, or 132? and how do you know they have not been "looked at"? what does "clean state" mean? We need to do something about this. why? My proposal to the group was - that everyone has a look at these tickets and updates the ones that are important. to whom, when? The ones no one is interested in should be handled as well - in my opinion closed - as no miracle happens here. i see your point; my objection is to "closed". just because nobody has yet taken an interest in ticket x does not mean nobody ever will. new people come on board, marking sth as "closed" will effectively make it invisible. case in pointe: eliminating comments that mix c and c++ comment syntax. completely trivial, nobody cares, mostly, and i have not had time to make a patch in the past 6 months. that does not mean it will never happen. don't you dare mark it as closed! i guess i do not understand what is driving this. i do not think a jira with lots of unaddressed tix is "dirty", so i do not see how "cleaning" it solves a real problem. to be blunt this strikes me as pure bureaucracy, sth only a project manager could love: reducing the number of open tix looks better to management. but there is no mgmt here. if you want to encourage people to resolve open tix i'm all for it, but you cannot force volunteers to do stuff that does not interest them. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170325/ace999c7/attachment.html>
