From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>,
Stefan Hajnoczi <stefan.hajnoczi@uk.ibm.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [RFC] 0.13.0 Release plan
Date: Tue, 18 May 2010 10:17:42 -0500 [thread overview]
Message-ID: <4BF2AF96.2010505@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100518115243.712650d4@redhat.com>
On 05/18/2010 09:52 AM, Luiz Capitulino wrote:
> On Tue, 18 May 2010 09:32:32 -0500
> Anthony Liguori<aliguori@linux.vnet.ibm.com> wrote:
>
>
>> Hi,
>>
>> Here's my current thinking for the 0.13.0 release. Since there's a lot
>> of activity going on with QMP, I'd like to move the release out to July 1st.
>>
>> Here's what I'd like to do between now and then:
>>
>> - Do a detailed review of the QMP specification by sending out
>> portions of the spec to the mailing list and waiting for at least 3 acks
>> (Stefan/Anthony)
>>
> Agreed.
>
> Actually I was wondering if this shouldn't be QMP's development plan,
> ie. any QMP change which is protocol visible, must:
>
> 1. Add the proper entry in qmp-commands.txt
> 2. Get three ACKs on the list
>
Yes, I think that's a good idea.
> Of course that we need qmp-commands.txt merged. Jan has just finished
> incorporating its contents in qemu-monitor.hx, now qmp-commands.txt is
> generated from there.
>
> I will fix the doc's reported problems in his series and submit it.
>
>
>> - Redesign QError to be more consistent (Markus/Luiz)
>>
> Yes, we have all issues pointed out by Avi too. I plan to look at them
> as soon as the document is merged.
>
> However, the ones used by libvirt should be considered with extra care.
>
>
>> - Host a bug day on June 1st (more details in later note)
>>
> Excellent idea, suggest asking in that thread if anyone volunteers to be
> the issue tracker's 'maintainer' (main job is bug triage).
>
If anyone volunteers, that would be great but it's definitely a tough job.
I'm going to setup a wiki page with some information about how to
participate in the Bug Day and then I'll send out another note later today.
Regards,
Anthony Liguori
>> - Freeze stable-0.13 on June 21st and release 0.13.0-rc
>> - Accept only bug fixes for stable-0.13
>> - 0.13.0-rc2 release on June 28th
>> - 0.13.0 release on July 1st
>>
> ACK
>
>
>> Any feedback and/or suggestions would be appreciated.
>>
>> Regards,
>>
>> Anthony Liguori
>>
>>
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Stefan Hajnoczi <stefan.hajnoczi@uk.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>,
Markus Armbruster <armbru@redhat.com>
Subject: [Qemu-devel] Re: [RFC] 0.13.0 Release plan
Date: Tue, 18 May 2010 10:17:42 -0500 [thread overview]
Message-ID: <4BF2AF96.2010505@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100518115243.712650d4@redhat.com>
On 05/18/2010 09:52 AM, Luiz Capitulino wrote:
> On Tue, 18 May 2010 09:32:32 -0500
> Anthony Liguori<aliguori@linux.vnet.ibm.com> wrote:
>
>
>> Hi,
>>
>> Here's my current thinking for the 0.13.0 release. Since there's a lot
>> of activity going on with QMP, I'd like to move the release out to July 1st.
>>
>> Here's what I'd like to do between now and then:
>>
>> - Do a detailed review of the QMP specification by sending out
>> portions of the spec to the mailing list and waiting for at least 3 acks
>> (Stefan/Anthony)
>>
> Agreed.
>
> Actually I was wondering if this shouldn't be QMP's development plan,
> ie. any QMP change which is protocol visible, must:
>
> 1. Add the proper entry in qmp-commands.txt
> 2. Get three ACKs on the list
>
Yes, I think that's a good idea.
> Of course that we need qmp-commands.txt merged. Jan has just finished
> incorporating its contents in qemu-monitor.hx, now qmp-commands.txt is
> generated from there.
>
> I will fix the doc's reported problems in his series and submit it.
>
>
>> - Redesign QError to be more consistent (Markus/Luiz)
>>
> Yes, we have all issues pointed out by Avi too. I plan to look at them
> as soon as the document is merged.
>
> However, the ones used by libvirt should be considered with extra care.
>
>
>> - Host a bug day on June 1st (more details in later note)
>>
> Excellent idea, suggest asking in that thread if anyone volunteers to be
> the issue tracker's 'maintainer' (main job is bug triage).
>
If anyone volunteers, that would be great but it's definitely a tough job.
I'm going to setup a wiki page with some information about how to
participate in the Bug Day and then I'll send out another note later today.
Regards,
Anthony Liguori
>> - Freeze stable-0.13 on June 21st and release 0.13.0-rc
>> - Accept only bug fixes for stable-0.13
>> - 0.13.0-rc2 release on June 28th
>> - 0.13.0 release on July 1st
>>
> ACK
>
>
>> Any feedback and/or suggestions would be appreciated.
>>
>> Regards,
>>
>> Anthony Liguori
>>
>>
>
next prev parent reply other threads:[~2010-05-18 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 14:32 [RFC] 0.13.0 Release plan Anthony Liguori
2010-05-18 14:32 ` [Qemu-devel] " Anthony Liguori
2010-05-18 14:52 ` Luiz Capitulino
2010-05-18 14:52 ` [Qemu-devel] " Luiz Capitulino
2010-05-18 15:17 ` Anthony Liguori [this message]
2010-05-18 15:17 ` Anthony Liguori
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=4BF2AF96.2010505@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefan.hajnoczi@uk.ibm.com \
/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.