Open Stack

Thanks, Stefano!

This is an excellent idea. I think the prod_wg is the perfect place to kick off the definition/creation of an OpenStack wide bugs dashboard, with weekly summary posted to dev, ops, prod_wg.

I can see an overall OpenStack big tent score, then a per project set of scores.

something like:

New in past week: [per class crit, high, med, wishlist, etc]
Open:  [per class]
Closed: [per class]
Avg time open: [per class]
Longest time open: [per class]

Then the same for backports.

I would also love to highlight all bugs and progress on them that span multiple projects.

What do you guys think?


> -----Original Message-----
> From: Stefano Maffulli [mailto:stefano at openstack.org]
> Sent: Friday, October 02, 2015 4:31 PM
> To: product-wg at lists.openstack.org
> Subject: Re: [Product] proposal for expediting bug fixes
> 
> On 09/29/2015 12:53 PM, Rochelle Grober wrote:
> > On the stable branch bugfix velocity
> [...]
> 
> This thread made me realize that we don't track bug velocity afaik.
> Checking the latest draft of the community quarterly report[1] and
> indeed, we have 3 metrics of velocity to merge code (only to the master
> branch) and only one metric for bugs (closed/open ratio).
> 
> If you think it's important to have such metrics, you can define them
> and discuss with the Foundation how to add them to the reporting engine
> of choice (whether it's stackalytics or the quarterly reports or
> activity.openstack.org or something else).
> 
> /stef
> 
> https://review.openstack.org/#/c/228879/1
> 
> _______________________________________________
> Product-wg mailing list
> Product-wg at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/product-wg