qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.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 11:52:43 -0300	[thread overview]
Message-ID: <20100518115243.712650d4@redhat.com> (raw)
In-Reply-To: <4BF2A500.7040609@linux.vnet.ibm.com>

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

 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).

>   - 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
> 

  reply	other threads:[~2010-05-18 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-18 14:32 [Qemu-devel] [RFC] 0.13.0 Release plan Anthony Liguori
2010-05-18 14:52 ` Luiz Capitulino [this message]
2010-05-18 15:17   ` [Qemu-devel] " 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=20100518115243.712650d4@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=kvm@vger.kernel.org \
    --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 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).