Gentoo Archives: gentoo-dev

From: Sebastian Pipping <sping@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [Gentoo Pheonix] Heartbeat team force
Date: Wed, 07 Apr 2010 11:20:57
In Reply to: [gentoo-dev] [Gentoo Pheonix] Heartbeat team force by Sebastian Pipping
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 ---------------------- Bug load per herd ----------------- Bugs in a tree of category and package -------------------------------------- Bugs that may lack mention of package name ------------------------------------------ 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:;a=summary Run the report generator as following: # bzip2 -d xmlbugs.xml.bz2 # python modules/heartbeat/ The .bz2 file needed is up at <>, too. Sebastian


Subject Author
Re: [gentoo-dev] [Gentoo Pheonix] Heartbeat team force "Robin H. Johnson" <robbat2@g.o>
Re: [gentoo-dev] [Gentoo Pheonix] Heartbeat team force Ben de Groot <yngwin@g.o>