Nicholas, this seems like it is leading somewhere very good. One thing that I wonder about right away is the stats for bug processing, like mean times to pass from one stage to the next; and how those means evolve.
I guess this is not really the business of QA per se but it seems like "knowing what happens after the bug is detetected" could be a strong motivator for us all. Chris Hermansen · [email protected] C'est ma façon de parler. On Apr 17, 2013 12:58 PM, "Nicholas Skaggs" <[email protected]> wrote: > I wanted to share with everyone a sneak preview of some data I've been > gathering to help us as a team visualize our work and impact. This work > will eventually *fingers crossed* land on reports.qa.ubuntu.com. Note > that this website is temporary and isn't the final home for this. It might > go off-line or disappear/not be up at times. I will do my best to keep the > site up, and it up to date with the latest results until they land on the > ubuntu qa dashboard. > > http://91.189.93.58/ > > Please let me know of ideas you might have or things/data you would want > to see as part of this. Currently I'm looking at trying to get data for the > following things: > > Top contributors in each area > Highlight potential problem ares in development release: > package with most new bugs in last X days > oldest un-run testcases > unconfirmed bugs opened by team members > least run testcases (packages, isos) > > Questions? Comments? Most of all I want to let everyone know about our > work as a team, what we've accomplished over the past cycle, etc. It's > exciting to see people step up and learn new things all while helping make > ubuntu better. Thanks everyone! > > Nicholas > > -- > Ubuntu-quality mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality > >
-- Ubuntu-quality mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
