From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LRjXJ-0008Ou-P2 for qemu-devel@nongnu.org; Tue, 27 Jan 2009 03:43:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LRjXI-0008NJ-DS for qemu-devel@nongnu.org; Tue, 27 Jan 2009 03:43:09 -0500 Received: from [199.232.76.173] (port=39246 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LRjXI-0008ND-2w for qemu-devel@nongnu.org; Tue, 27 Jan 2009 03:43:08 -0500 Received: from mx2.redhat.com ([66.187.237.31]:37802) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LRjXH-0001xi-JO for qemu-devel@nongnu.org; Tue, 27 Jan 2009 03:43:07 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n0R8h43V001681 for ; Tue, 27 Jan 2009 03:43:06 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n0R8h4eq029364 for ; Tue, 27 Jan 2009 03:43:04 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n0R8h3i7008885 for ; Tue, 27 Jan 2009 03:43:04 -0500 Subject: Re: [Qemu-devel] Qemu Trac? From: Mark McLoughlin In-Reply-To: <497E60DC.7010203@codemonkey.ws> References: <497E60DC.7010203@codemonkey.ws> Content-Type: text/plain Date: Tue, 27 Jan 2009 08:43:02 +0000 Message-Id: <1233045782.4789.38.camel@blaa> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: Mark McLoughlin , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Mon, 2009-01-26 at 19:18 -0600, Anthony Liguori wrote: > C.W. Betts wrote: > > Is there a trac or something similar that keeps track of bug reports > > and feature requests? > > No. KVM has a bug tracker. Each distro has bug trackers too. To be > completely honest, the distro bug trackers are probably the best place > to file bugs simply because they have people who's job it is to poke > upstream developers about particular bugs :-) Of course, that requires > reproducing with the distro packages. An upstream bug tracker is much more preferable IMHO. Distro bug trackers are only good for tracking stuff that distro developers might actually work on. If it's a bug or feature request that is relevant upstream and is never going to reach the top of the distro developer's queue, then the information belongs somewhere that upstream developers or developers of other distros can see it. Of course, an upstream bug tracker that is mostly ignored isn't much help either. The KVM tracker is an example of that. But it's still better to have stuff ignored in an upstream bug tracker than stuff ignored in a distro bug tracker. Cheers, Mark.