From: Anthony Liguori <anthony@codemonkey.ws>
To: Brian Jackson <iggy@theiggy.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for May 18
Date: Tue, 18 May 2010 17:08:36 -0500 [thread overview]
Message-ID: <4BF30FE4.8010501@codemonkey.ws> (raw)
In-Reply-To: <201005181634.43770.iggy@theiggy.com>
On 05/18/2010 04:34 PM, Brian Jackson wrote:
> A lot of the existing bugs are irrelevant and/or woefully out of date. I've
> been hesitant to go back and mess with too many old bugs for fear of making
> too much noise that I know isn't going to do anything useful (i.e. marking the
> 100 oldest bugs as Closed - Out Of Date)
>
One activity for bug day should be migrating bugs from SF to Launchpad
that can be confirmed. I don't know if SF has an expiration mechanism,
but on Launchpad, you can mark a bug as needs info and if it isn't
updated in 90 days, it automatically expires.
>> - need more people involved w/ bug work
>>
>
> And need a better way for those of us that do to be able to get ahold of devs
> to look at things that are actually important to users.
>
Part of the idea of bug day is to get devs in an IRC channel so that
people can ask questions in real time about bugs.
>
>> - possible bug-day before next release
>> - suggested June 1st
>>
>
> Personally (and in general for volunteer projects), weekends are better for
> bugs days. That said, I realize that most of the developers for qemu/kvm do
> this for their day job.
>
Not everyone has the same weekend due to TZ/country differences. That
said, if the first bug day is successful, we can hold more and try to
accommodate different groups of people.
Regards,
Anthony Liguori
>
>> 0.12.4 bugs
>> - migration regression...follow-up on email, open a bug ;-)
>> --
>> To unsubscribe from this list: send the line "unsubscribe kvm" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2010-05-18 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 14:29 [Qemu-devel] KVM call minutes for May 18 Chris Wright
2010-05-18 21:34 ` [Qemu-devel] " Brian Jackson
2010-05-18 22:08 ` Anthony Liguori [this message]
2010-05-19 17:02 ` Avi Kivity
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=4BF30FE4.8010501@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=iggy@theiggy.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).