Re: KVM call minutes for May 18

[Anthony Liguori <anthony@codemonkey.ws>]

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
>