Re: bug tracking?

[Patrick Shirkey <pshirkey@boosthardware.com>]

Takashi Iwai wrote:
>>
>>The question is, if we have power to maintain such large bug reports.
>>From my experience, it works only few weeks until the system has many 
>>unresolved reports. Then the database gets filled and only some bugs are 
>>solved when our time permits. Also, when the database is large, it is
>>a bit problematic to mark solved reports (especially old ones).
> 

We also have the added difficulty of making sure each driver is 
adaquately covered by the system.

> - no template for necessary information
> 
>   e.g. alsa version, driver, chip/board name/model, output of lspci
>        output of proc files, etc.
> 

These could easily be found with a simple script or maybe there couold 
be an alsa.debug file in /proc/asound.

> 
> also, a moderator person would be helpful in addition to the automatic
> assignment according to the given driver/function.
> 

How about having a bugs mailing list and also the address of the driver 
writer. We could then post the report to the mailing list, the driver 
writer and also archive it on the alsa website.

I will start making a bugs page over the next few days which we can fine 
tune here. I'm not sure that bugzilla is appropriate for ALSA as we have 
so many different devices to look after however I will use it as a 
reference.


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com