From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Cole Robinson <crobinso@redhat.com>
Subject: Re: KVM call agenda for July 27
Date: Tue, 27 Jul 2010 08:30:10 -0500 [thread overview]
Message-ID: <4C4EDF62.4070702@codemonkey.ws> (raw)
In-Reply-To: <20100727115109.GN12387@redhat.com>
On 07/27/2010 06:51 AM, Daniel P. Berrange wrote:
> On Mon, Jul 26, 2010 at 05:28:21PM -0500, Anthony Liguori wrote:
>
>> On 07/26/2010 04:28 PM, Chris Wright wrote:
>>
>>> Please send in any agenda items you are interested in covering.
>>>
>>>
>> - 0.13 update
>> I'll pre-empt the 0.13 question with an answer. I'm just testing the
>> VNC changes and if all goes well, I'll tag tonight.
>>
>> Initial thinking is to keep 0.14 short and target Dec 1st.
>>
>> - if danpb can make it, would like to discuss -help output parsing
>> summary: help parsing is terrible, but given the fact that
>> capabilities is going to take a while to get totally right, would like
>> to discuss an interim solution that gives us more flexibility to do
>> reasonable things with the help output.
>>
> I'm not able to make this call today& next week i'm on PTO
No problem. Enjoy your holiday.
> . I would
> like to think that we could get a suitable capabilities sytem in place
> for 0.14 release. Since 0.13 is nearly ready& libvirt works with it
> aside from the cache issue which is now addressed in libvirt, I don't
> think its useful to change libvirt further.
So 0.8.2 is broken or did 0.8.2 get fixed?
What changes would need to be made for 0.13 to work with existing
versions of libvirt?
If we can agree that 0.13 is the last time we make these changes, I'd be
willing to do it one more time. I'd strongly suggest switching
eliminating the help parsing entirely instead of just waiting for
capabilities.
> We need to just focus on
> getting capabilities (and QMP in general for that matter) ready for
> 0.14 and not let it slip still further into 0.15.
>
No objections on my side.
Regards,
Anthony Liguori
> Regards,
> Daniel
>
next prev parent reply other threads:[~2010-07-27 13:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:28 KVM call agenda for July 27 Chris Wright
2010-07-26 22:28 ` Anthony Liguori
2010-07-26 23:28 ` Anthony Liguori
2010-07-27 0:13 ` Alex Williamson
2010-07-27 13:22 ` Jes Sorensen
2010-07-27 7:19 ` Markus Armbruster
2010-07-27 13:00 ` Anthony Liguori
2010-07-27 13:28 ` [Qemu-devel] " Kevin Wolf
2010-07-27 15:22 ` Markus Armbruster
2010-07-27 15:28 ` Anthony Liguori
2010-07-27 15:37 ` Daniel P. Berrange
2010-07-27 16:17 ` Avi Kivity
2010-07-27 16:24 ` Daniel P. Berrange
2010-07-27 16:29 ` Chris Wright
2010-07-27 16:32 ` Avi Kivity
2010-07-27 16:36 ` Chris Wright
2010-07-27 16:42 ` Avi Kivity
2010-07-27 17:01 ` Daniel P. Berrange
2010-07-27 17:37 ` Avi Kivity
2010-07-27 16:42 ` Daniel P. Berrange
2010-07-27 16:47 ` Avi Kivity
2010-07-27 16:48 ` Avi Kivity
2010-07-28 11:22 ` Markus Armbruster
2010-07-28 11:25 ` Kevin Wolf
2010-07-28 13:08 ` Markus Armbruster
2010-07-27 11:51 ` Daniel P. Berrange
2010-07-27 13:30 ` Anthony Liguori [this message]
2010-07-27 13:43 ` Cole Robinson
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=4C4EDF62.4070702@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=berrange@redhat.com \
--cc=chrisw@redhat.com \
--cc=crobinso@redhat.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