[openstack-dev] Grizzly's out - let the numbers begin...

Thierry Carrez thierry at openstack.org
Mon Apr 22 12:01:18 UTC 2013


Jesus M. Gonzalez-Barahona wrote:
> In addition, we're tracking time-to-close for tickets, and there the
> difference between committed and released matters, because times are
> different. When do you think a ticket should be considered as closed? At
> "Fix committed" or at "Fix released" time?

At "fix committed", see below.

> Right now, the condition for considering a ticket as closed is:
> 
> new_value = 'Fix Released' or new_value = 'Invalid' or new_value =
> 'Expired' or new_value = 'Won\'t Fix'
> 
> Do you find this ok? Any other state?

I think "Fix Committed" should be considered "closed" too. We switch
from FixCommitted to FixReleased when the fix is shipped into a
development milestone (roughly every 6 weeks), so it would alter your
time-to-close stats significantly if you just considered "FixReleased".

"Opinion" is also a "closed" state in Launchpad. We don't really have a
large use of those, but for completeness I would also add it to your query.

-- 
Thierry Carrez (ttx)
Release Manager, OpenStack



More information about the OpenStack-dev mailing list