From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [RFC] Bug Day - June 1st, 2010
Date: Wed, 19 May 2010 11:52:01 -0300 [thread overview]
Message-ID: <20100519115201.193e2efd@redhat.com> (raw)
In-Reply-To: <4BF316E3.6020002@linux.vnet.ibm.com>
On Tue, 18 May 2010 17:38:27 -0500
Anthony Liguori <aliguori@linux.vnet.ibm.com> wrote:
> Hi,
>
> In an effort to improve the 0.13 release quality, I'd like to host a Bug
> Day on June 1st, 2010. I've setup a quick wiki page with some more info
> (http://wiki.qemu.org/BugDay/June2010).
Tuesday is our call conf day and other people have reported that they have
more confs during that day. Suggest Jun 2.
> Here's my basic thinking:
>
> - Anyone who can should try to spend some time either triaging bugs,
> updating bug status, or actually fixing bugs.
And testing, Fedora has a number of test cases already written, but
I guess that just a few are qemu specific:
https://fedoraproject.org/wiki/Test_Day:2010-04-08_Virtualization
We could link those and write our own, or at least list the major
features to be tested..
Of course we could have a different day for testing too, but I think
this is a way to get everyone busy.
> - We'll have a special IRC channel (#qemu-bugday) on OFTC. As many
> QEMU and KVM developers as possible should join this channel for that
> day to help assist people working on bugs.
> - We'll try to migrate as many confirmable bugs from the Source Forge
> tracker to Launchpad.
Can't this be automated?
> If this is successful, we'll try to have regular bug days. Any
> suggestions on how to make the experience as fun and productive as
> possible are certainly appreciated!
Lots of foods and a Monty Python session in the evening.
next prev parent reply other threads:[~2010-05-19 14:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 22:38 [RFC] Bug Day - June 1st, 2010 Anthony Liguori
2010-05-18 22:38 ` [Qemu-devel] " Anthony Liguori
2010-05-19 0:58 ` Natalia Portillo
2010-05-19 1:45 ` Jamie Lokier
2010-05-19 1:48 ` Natalia Portillo
2010-05-19 1:48 ` [Qemu-devel] " Natalia Portillo
2010-05-19 13:35 ` Anthony Liguori
2010-05-19 13:35 ` [Qemu-devel] " Anthony Liguori
2010-05-19 14:10 ` Natalia Portillo
2010-05-19 14:10 ` Natalia Portillo
2010-05-19 13:09 ` Anthony Liguori
2010-05-19 13:09 ` [Qemu-devel] " Anthony Liguori
2010-05-19 13:19 ` Michael Tokarev
2010-05-19 13:19 ` Michael Tokarev
2010-05-19 13:32 ` Anthony Liguori
2010-05-19 13:32 ` Anthony Liguori
2010-05-19 15:57 ` Jamie Lokier
2010-05-19 15:57 ` Jamie Lokier
2010-05-19 22:29 ` Andre Przywara
2010-05-19 22:29 ` Andre Przywara
2010-05-19 22:30 ` Anthony Liguori
2010-05-19 22:30 ` Anthony Liguori
2010-05-20 5:58 ` Michael Tokarev
2010-05-20 7:15 ` Andre Przywara
2010-05-20 7:15 ` Andre Przywara
2010-05-20 21:32 ` Michael Tokarev
2010-05-20 21:32 ` Michael Tokarev
2010-05-19 14:06 ` Natalia Portillo
2010-05-19 14:06 ` Natalia Portillo
2010-05-20 7:43 ` Jes Sorensen
2010-05-19 5:04 ` Aurelien Jarno
2010-05-19 12:21 ` Miguel Di Ciurcio Filho
2010-05-19 13:34 ` Anthony Liguori
2010-05-20 7:50 ` Jes Sorensen
2010-05-20 7:50 ` Jes Sorensen
2010-05-19 14:52 ` Luiz Capitulino [this message]
2010-05-19 17:02 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2010-05-19 14:17 Riccardo Magliocchetti
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=20100519115201.193e2efd@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@linux.vnet.ibm.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 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.