All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Mark McLoughlin <markmc@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu Trac?
Date: Tue, 27 Jan 2009 08:41:26 -0600	[thread overview]
Message-ID: <497F1D16.8060502@codemonkey.ws> (raw)
In-Reply-To: <1233045782.4789.38.camel@blaa>

Mark McLoughlin wrote:
> 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.
>   

I, and I expect many other developers, have a hard time getting excited 
about bug trackers.  I think something that's a bit more exciting is an 
regression suite that posts results somewhere public.  It makes it 
harder to submit bug reports (because it requires submission of a test 
case), but it makes triage/state tracking automatic.

If someone wants to invest some effort into improving QEMU QA, I'd 
suggest looking at automated regression testing.

Regards,

Anthony Liguori

> Cheers,
> Mark.
>
>
>
>   

      reply	other threads:[~2009-01-27 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27  0:53 [Qemu-devel] Qemu Trac? C.W. Betts
2009-01-27  0:53 ` C.W. Betts
2009-01-27  1:18   ` Anthony Liguori
2009-01-27  8:43     ` Mark McLoughlin
2009-01-27 14:41       ` Anthony Liguori [this message]

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=497F1D16.8060502@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=markmc@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.