From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MItOK-0006TS-CM for qemu-devel@nongnu.org; Mon, 22 Jun 2009 19:57:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MItOF-0006Oy-DN for qemu-devel@nongnu.org; Mon, 22 Jun 2009 19:57:35 -0400 Received: from [199.232.76.173] (port=38851 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MItOF-0006OS-7z for qemu-devel@nongnu.org; Mon, 22 Jun 2009 19:57:31 -0400 Received: from e2.ny.us.ibm.com ([32.97.182.142]:60247) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MItOE-0003iL-Q0 for qemu-devel@nongnu.org; Mon, 22 Jun 2009 19:57:30 -0400 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e2.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n5MNqgLe029885 for ; Mon, 22 Jun 2009 19:52:42 -0400 Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by d01relay04.pok.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n5MNvRlK220386 for ; Mon, 22 Jun 2009 19:57:27 -0400 Received: from d01av02.pok.ibm.com (loopback [127.0.0.1]) by d01av02.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n5MNt6lY024040 for ; Mon, 22 Jun 2009 19:55:06 -0400 Message-ID: <4A401A65.3080804@us.ibm.com> Date: Mon, 22 Jun 2009 18:57:25 -0500 From: Anthony Liguori MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Planning for the 0.11.0 release List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org" , kvm-devel Hi, It's getting to be about the time to start thinking about the 0.11.0 release. 0.10.0 was released on March 2nd so following with the 6 month release cycle, that would put 0.11.0 at September 2nd. Based on the experiences with the stable releases, here's what I'd recommend: o On July 15th, fork master -> stable-0.11 o Change version to 0.10.90 o Release qemu-0.11.0-rc1 o Release additional -rcN releases every 1-2 weeks o Introduce a new maintainer for stable-0.10 (via git pulls) o At least 1 week before release, hopefully we'll have the final -rcN that we can then declare 0.11.0. I think we should really try hard to make these dates. I only have a few things that I would like to see happen before forking stable-0.11. Namely: o Setup qemu.org infrastructure (git hosting, wiki) o Setup qemu bug tracker (see next mail) o Include all ROM source code in tree via git submodules. This is a major headache for distributors and I think it's important to resolve before our next release. o Disable kqemu by default. The intention is _not_ to remove kqemu support. Enabling kqemu by default causes a few unpleasant side effects including errors if -m is greater than 1/2 of the host physical memory. I don't expect the qdev conversion will be complete by 0.11. I think we should try to get as much of the invasive changes as possible in to make stable-0.11 as maintainable as possible. However, I think it would be a mistake to gate the release on qdev. -- Regards, Anthony Liguori