[Libreoffice-qa] Unconfirmed Bug Count (Promising #'s)

Bjoern Michaelsen bjoern.michaelsen at canonical.com
Tue Jan 7 05:28:39 PST 2014


On Tue, Jan 07, 2014 at 01:58:45PM +0100, Tommy wrote:
> see also this chart:
> http://snipurl.com/28ew3u5

Looking at that and other charts, some guestimates:
- QA is doing great at confirming bugs from UNCONFIRMED->NEW as UNCONFIRMED
  goes down
- QA/development is precise in telling people what is needed as NEEDINFO stays
  constant
- development fixes ~1000 issues in 6 months (one release cycle) which is good
- QA finds some ~1000 duplicates in 6 months (one release cycle) which is also
  good 
- QA closes some ~1000 issues as invalid in 6 months (one release cycle) which
  is good too
- our NEW bug count is still growing, but is slowing down and now at ~1000 more
  bugs in NEW in the last 8 months

So both QA and development are doing a really good job and are getting better
and better. Ideally, we should get the NEW count (excluding enhancement
requests) to be constant too: we are not quite there yet, but improving. And
with currently 1487 of the 6407 NEW bugs being actually enhancement requests,
the stats are somewhat muddy there.

Best,

Bjoern


More information about the Libreoffice-qa mailing list