Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Sebastian Pipping <sping@g.o>
Subject: Re: [Gentoo Pheonix] Heartbeat team force
Date: Wed, 07 Apr 2010 13:20:11 +0200
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


Replies:
Re: [Gentoo Pheonix] Heartbeat team force
-- Robin H. Johnson
Re: [Gentoo Pheonix] Heartbeat team force
-- Ben de Groot
References:
[Gentoo Pheonix] Heartbeat team force
-- Sebastian Pipping
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Re: [Gentoo Pheonix] Heartbeat team force
Next by thread:
Re: [Gentoo Pheonix] Heartbeat team force
Previous by date:
Re: [git migration] The problem of ChangeLog generation
Next by date:
Re: [Gentoo Pheonix] Heartbeat team force


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.