public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [Gentoo Pheonix] Heartbeat team force
Date: Wed, 07 Apr 2010 13:20:11 +0200	[thread overview]
Message-ID: <4BBC6A6B.5080804@gentoo.org> (raw)
In-Reply-To: <4BB7C02D.7090008@gentoo.org>

On 04/04/10 00:24, Sebastian Pipping wrote:
> Concrete tasks
> ==============
> - [..]
> - work on association between bugs and packages
>   (for all bugs, not just bugday ones)

I've been playing with code answering the questions:
- How do bugs and packages relate?
- How is bugload distributed across developers?

I came to a point where
- I have something that starts to be useful
- I am facing troubles that need further
  consideration first, see below.


Current results
===============
Bug load per developer
----------------------
http://dev.gentoo.org/~sping/bug-heartbeat/report--bug-count-by-person.html

Bug load per herd
-----------------
http://dev.gentoo.org/~sping/bug-heartbeat/report--bug-count-by-herd.html

Bugs in a tree of category and package
--------------------------------------
http://dev.gentoo.org/~sping/bug-heartbeat/report--bugs-by-package.html

Bugs that may lack mention of package name
------------------------------------------
http://dev.gentoo.org/~sping/bug-heartbeat/report--bugs-without-package.html


Question to be answered
=======================
 - herds.xml does not hold membership lists for
   all projects, not even herds.  The load
   evaluator needs access to complete mappings
   to generate output close to reality.
   How can such a mapping be made without
   duplicating data?

 - Pulling XML out of Bugzilla does no longer
   feel right with this amount of data:
   it's 15,000 open bugs that need to be
   refreshed periodically in chunks of 100 bugs
   (Bugzilla's limit) each.  That's 150 request
   for a full sync.  How can that be improved?


Generating reports yourself
===========================
In case you want to play with the code yourself:
http://git.goodpoint.de/?p=gentoo-bug-heartbeat.git;a=summary

Run the report generator as following:

  # bzip2 -d xmlbugs.xml.bz2
  # python modules/heartbeat/reporter.py

The .bz2 file needed is up at
<http://dev.gentoo.org/~sping/bug-heartbeat/>, too.



Sebastian



  parent reply	other threads:[~2010-04-07 11:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 22:24 [gentoo-dev] [Gentoo Pheonix] Heartbeat team force Sebastian Pipping
2010-04-03 22:30 ` Jesus Rivero (Neurogeek)
2010-04-03 22:57   ` Sebastian Pipping
2010-04-04  3:09     ` Jesus Rivero (Neurogeek)
2010-04-03 22:42 ` Alec Warner
2010-04-03 22:59   ` Sebastian Pipping
2010-04-06  7:03 ` [gentoo-dev] " Torsten Veller
2010-04-07 16:41   ` Markos Chandras
2010-04-07 11:20 ` Sebastian Pipping [this message]
2010-04-07 12:00   ` [gentoo-dev] " Ben de Groot
2010-04-07 18:55     ` Sebastian Pipping
2010-04-07 19:24       ` Ben de Groot
2010-04-08 10:57         ` Sebastian Pipping
2010-04-08 11:09           ` [gentoo-dev] " Torsten Veller
2010-04-08 19:16   ` [gentoo-dev] " Robin H. Johnson
2010-04-08 21:22     ` Sebastian Pipping

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BBC6A6B.5080804@gentoo.org \
    --to=sping@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox