Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-15 Thread Anthony Liguori
On 07/15/2010 01:51 PM, Aurelien Jarno wrote: On Thu, Jul 15, 2010 at 01:43:28PM -0500, Justin M. Forbes wrote: On Tue, Jul 13, 2010 at 12:19:21PM -0500, Brian Jackson wrote: On Tuesday, July 13, 2010 12:01:22 pm Avi Kivity wrote: On 07/13/2010 07:57 PM, Anthony Liguori wrote

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-15 Thread Aurelien Jarno
On Thu, Jul 15, 2010 at 01:43:28PM -0500, Justin M. Forbes wrote: > On Tue, Jul 13, 2010 at 12:19:21PM -0500, Brian Jackson wrote: > > On Tuesday, July 13, 2010 12:01:22 pm Avi Kivity wrote: > > > On 07/13/2010 07:57 PM, Anthony Liguori wrote: > > > >> I'd like to see more frequent stable releases,

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-15 Thread Justin M. Forbes
On Tue, Jul 13, 2010 at 12:19:21PM -0500, Brian Jackson wrote: > On Tuesday, July 13, 2010 12:01:22 pm Avi Kivity wrote: > > On 07/13/2010 07:57 PM, Anthony Liguori wrote: > > >> I'd like to see more frequent stable releases, at least if the stable > > >> branch contains fixes to user-reported bugs

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-13 Thread Avi Kivity
On 07/13/2010 08:19 PM, Brian Jackson wrote: Yes. But in this context I'm interested in stable releases. We have bugs reported, fixed, and the fix applied, yet the fixes are unreachable to users. Especially so since qemu-kvm 0.12-stable hasn't been merged with qemu basically since 0.12

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-13 Thread Brian Jackson
On Tuesday, July 13, 2010 12:01:22 pm Avi Kivity wrote: > On 07/13/2010 07:57 PM, Anthony Liguori wrote: > >> I'd like to see more frequent stable releases, at least if the stable > >> branch contains fixes to user-reported bugs (or of course security or > >> data integrity fixes). > > > > Would y

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-13 Thread Avi Kivity
On 07/13/2010 07:57 PM, Anthony Liguori wrote: I'd like to see more frequent stable releases, at least if the stable branch contains fixes to user-reported bugs (or of course security or data integrity fixes). Would you like to see more frequent stable releases or more frequent master releas

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-13 Thread Anthony Liguori
On 07/13/2010 02:40 AM, Avi Kivity wrote: On 07/13/2010 09:57 AM, Aurelien Jarno wrote: Avi Kivity a écrit : On 07/12/2010 05:57 PM, Juan Quintela wrote: Please send in any agenda items you are interested in covering. 0.12.n+1 I won't be at the KVM call, but I can work on that in the next

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-13 Thread Avi Kivity
On 07/13/2010 05:08 PM, Luiz Capitulino wrote: I'd like to see more frequent stable releases, at least if the stable branch contains fixes to user-reported bugs (or of course security or data integrity fixes). I remember someone has stepped in to take that work, but I don't exactly remem

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-13 Thread Luiz Capitulino
On Tue, 13 Jul 2010 10:40:40 +0300 Avi Kivity wrote: > On 07/13/2010 09:57 AM, Aurelien Jarno wrote: > > Avi Kivity a écrit : > > > >> On 07/12/2010 05:57 PM, Juan Quintela wrote: > >> > >>> Please send in any agenda items you are interested in covering. > >>> > >>> > >>> > >> 0

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-13 Thread Avi Kivity
On 07/13/2010 09:57 AM, Aurelien Jarno wrote: Avi Kivity a écrit : On 07/12/2010 05:57 PM, Juan Quintela wrote: Please send in any agenda items you are interested in covering. 0.12.n+1 I won't be at the KVM call, but I can work on that in the next days. Basically t

Re: [Qemu-devel] Re: KVM Call agenda for July 13th

2010-07-12 Thread Aurelien Jarno
Avi Kivity a écrit : > On 07/12/2010 05:57 PM, Juan Quintela wrote: >> Please send in any agenda items you are interested in covering. >> >> > > 0.12.n+1 > I won't be at the KVM call, but I can work on that in the next days. Basically the stable tree already contains a lot of fixes and we c