From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LWVUB-0000b7-Pr for qemu-devel@nongnu.org; Mon, 09 Feb 2009 07:43:39 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LWVUA-0000Z6-2O for qemu-devel@nongnu.org; Mon, 09 Feb 2009 07:43:39 -0500 Received: from [199.232.76.173] (port=50774 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LWVU9-0000Yv-SF for qemu-devel@nongnu.org; Mon, 09 Feb 2009 07:43:37 -0500 Received: from mx2.redhat.com ([66.187.237.31]:45634) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LWVU9-00009n-Dr for qemu-devel@nongnu.org; Mon, 09 Feb 2009 07:43:37 -0500 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n19ChaoR014215 for ; Mon, 9 Feb 2009 07:43:36 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n19ChaWN020173 for ; Mon, 9 Feb 2009 07:43:36 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n19ChZjW029873 for ; Mon, 9 Feb 2009 07:43:36 -0500 Subject: Re: [Qemu-devel] Cutting a new QEMU release From: Mark McLoughlin In-Reply-To: <4988AD96.6090308@codemonkey.ws> References: <4988AD96.6090308@codemonkey.ws> Content-Type: text/plain Date: Mon, 09 Feb 2009 12:43:34 +0000 Message-Id: <1234183414.13728.30.camel@blaa> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: Mark McLoughlin , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, 2009-02-03 at 14:48 -0600, Anthony Liguori wrote: > What do people think? TCG seems to be in a good place. We've got > virtio, KVM, live migration, tons of new devices, bsd-user, etc. > > We could decide to cut one by the end of the month. I'm already doing > some test work in QEMU so I can follow up with some more detailed notes > about what is working and what isn't working. That gives us some time > to decide if there's anything we need to fix before a release. Sounds great to me. >>From a Fedora perspective, qemu-0.9.1 is a year old and upstream has moved on a lot. As a package maintainer, it's hard to justify caring too much about bugs reported against 0.9.1, since the bug is likely to have very little relevance to the latest upstream. Also, it would be really nice to have a kvm-userspace based off a solid qemu release ... qemu moving so fast is great, but it means it's hard to predict the stability of a given kvm-userspace release. Some questions: - Will there be a period before the release when only bug fixes are merged? - Will there be a release candidate? - Is there any missing features that we might push out the release date for? - Post-release, is there any interest in maintaining a stable branch until the next release? - The plan for the next release is roughly 6 months, yes? Thanks, Mark.