Public data about product quality (in terms of conformance to specs) would
be useful, I agree. Especially if the measurements are standardized across
products.
Pine
On May 31, 2016 19:24, "Danny B." <Wikipedia.Danny.B(a)email.cz> wrote:
---------- Původní zpráva ----------
Od: Pine W <wiki.pine(a)gmail.com>
Komu: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Datum: 1. 6. 2016 4:02:40
Předmět: Re: [Wikitech-l] Phabricator monthly statistics - 2016-05
"Just to add to Bartosz's comment, the definition of tasks in Phabricator
includes feature requests, so more tasks may or may not correlate with more
problems.
Someone in QA may be able to comment with more detail about the number,
severity or percentage of problems relative to the number of tickets, and
the general quality trends of MediaWiki.
"
If tasks were properly triaged and tagged, it would be easy to create
various quite accurate statistics. But attempts to create tags which would
allow it were and are unfortunatelly being questioned, delayed, stalled or
even declined.
In one of my previous jobs, where I was taking care of the bugtracker as a
part of my duty, after I made an order in it, the number of opened tasks
decreased to nearly 70% of the original count. Then after some statistics
I'
ve ran from the new data, our teams became more effective and productive
due
to having better data to work with and at the end of the consolidation
process, we ended up in oscilating between 30-50% of the original amount of
opened tasks.
I wish it was possible to achieve the same here...
--
Danny B.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l