qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: kvm-devel <kvm@vger.kernel.org>,
	Dustin Kirkland <kirkland@canonical.com>
Subject: [Qemu-devel] QEMU bug tracker on Launchpad
Date: Mon, 22 Jun 2009 19:03:49 -0500	[thread overview]
Message-ID: <4A401BE5.2070805@us.ibm.com> (raw)

Dustin Kirkland was kind enough to setup a bug tracker for QEMU on 
Launchpad.  I would like to make this the official QEMU bug tracker 
unless there is significant objection.

There are a number of QEMU/KVM bug trackers mostly distribution centric 
today.  Having a common upstream bug tracker will help immensely in 
coordinating bug fixing effort for those people who are interested in 
that sort of thing :-)

Here are some of the requirements I had for a bug tracker in no 
particular order:

 1) minimal work required for the QEMU maintainers
 2) ability to link bugs to external bug trackers
 3) ability to control bug status via mails
 4) API for scripting

The biggest issue for me with Launchpad was that it is not open source 
today.  Canonical is actively working to release the source code though 
and have scheduled a date for release this July.  See the link below for 
more information.

I've already begun using this bug tracker so you can look through it 
today to get a feeling for what it's like.

https://bugs.launchpad.net/qemu
https://bugs.launchpad.net/qemu/+bugs
https://dev.launchpad.net/OpenSourcing

-- 
Regards,

Anthony Liguori

             reply	other threads:[~2009-06-23  0:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23  0:03 Anthony Liguori [this message]
2009-06-23 17:02 ` [Qemu-devel] QEMU bug tracker on Launchpad Blue Swirl
2009-06-23 17:09   ` Dustin Kirkland

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=4A401BE5.2070805@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=kirkland@canonical.com \
    --cc=kvm@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).