From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MJ8EF-0001qv-Oy for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:48:11 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MJ8EA-0001nh-TF for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:48:11 -0400 Received: from [199.232.76.173] (port=53309 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MJ8EA-0001nN-En for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:48:06 -0400 Received: from e8.ny.us.ibm.com ([32.97.182.138]:53180) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MJ8E9-00087K-HZ for qemu-devel@nongnu.org; Tue, 23 Jun 2009 11:48:06 -0400 Received: from d01relay06.pok.ibm.com (d01relay06.pok.ibm.com [9.56.227.116]) by e8.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n5NFbKrm002723 for ; Tue, 23 Jun 2009 11:37:20 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d01relay06.pok.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n5NFm3j11642524 for ; Tue, 23 Jun 2009 11:48:03 -0400 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n5NFlx5W006483 for ; Tue, 23 Jun 2009 09:47:59 -0600 Message-ID: <4A40F92E.1070108@us.ibm.com> Date: Tue, 23 Jun 2009 10:47:58 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Planning for the 0.11.0 release References: <4A401A65.3080804@us.ibm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: "qemu-devel@nongnu.org" , kvm-devel Blue Swirl wrote: > On 6/23/09, Anthony Liguori wrote: > >> 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. >> > > Sounds OK. I think OpenBIOS releases should follow similar schedule, > maybe even with matching SVN tags (1.1-rc1 for 0.11.0-rc1 etc). > > >> 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. >> > > I think this is great, but OpenBIOS still uses Subversion. Can git use > SVN submodules for example? > No, but it's not too hard to make svn->git bridges. Regards, Anthony Liguori -- Regards, Anthony Liguori