Hi,

One of the topics discussed during the last Qt contributor summit was the 
cleanup of our bug database. If you are interested in the outcomes check out:

https://qt-project.org/groups/qt-contributors-summit-2014/wiki/Expiring_Bugs

Finally I got some time to take care of the results. My plan is to perform 
these expiries on Friday this week.

The first step will be the closure of all bugs (and only bugs) in the "Need 
more info" state which have not seen any activity for the last year. An 
appropriate comment will be added to each Jira bug explaining the action and 
advising people how to react to it depending on their circumstances.

The second step is the transition of Unassigned bugs to the "Need more info" 
state if they have not seen any update during the last year. A comment will go 
along with the transition. 

You can avoid this happening to "your" important bugs by means of touching 
them. Also, feel free to revert some transitions as you may see fit in your 
work area.

Going forward I will repeat this in regular intervals (3 months) and reduce the 
"no update received" timeout to six and later three month in the case of of 
tasks in the "Need more info" state. This should result in a eventual setup 
whereby Unassiged/reported bugs expire after 12 months and "Need more info" 
bugs expire after 3 months.

If there are major objections to the proposed target for this week please raise 
them now.
--
Alex
_______________________________________________
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to