From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=60172 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OEOAb-0001FZ-Gg for qemu-devel@nongnu.org; Tue, 18 May 2010 10:53:23 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OEOAR-0004Ut-Du for qemu-devel@nongnu.org; Tue, 18 May 2010 10:53:18 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7193) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OEOAQ-0004U7-5n for qemu-devel@nongnu.org; Tue, 18 May 2010 10:53:11 -0400 Date: Tue, 18 May 2010 11:52:43 -0300 From: Luiz Capitulino Message-ID: <20100518115243.712650d4@redhat.com> In-Reply-To: <4BF2A500.7040609@linux.vnet.ibm.com> References: <4BF2A500.7040609@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [RFC] 0.13.0 Release plan List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Stefan Hajnoczi , qemu-devel , kvm-devel , Markus Armbruster On Tue, 18 May 2010 09:32:32 -0500 Anthony Liguori 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 >