From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LWdoQ-0005Aq-10 for qemu-devel@nongnu.org; Mon, 09 Feb 2009 16:37:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LWdoO-00055V-13 for qemu-devel@nongnu.org; Mon, 09 Feb 2009 16:37:05 -0500 Received: from [199.232.76.173] (port=33820 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LWdoN-000559-T9 for qemu-devel@nongnu.org; Mon, 09 Feb 2009 16:37:03 -0500 Received: from mail-gx0-f17.google.com ([209.85.217.17]:38407) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LWdoN-00079g-Jw for qemu-devel@nongnu.org; Mon, 09 Feb 2009 16:37:03 -0500 Received: by gxk10 with SMTP id 10so19985gxk.10 for ; Mon, 09 Feb 2009 13:37:02 -0800 (PST) Message-ID: <4990A1E5.8050809@codemonkey.ws> Date: Mon, 09 Feb 2009 15:36:37 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Cutting a new QEMU release References: <4988AD96.6090308@codemonkey.ws> <1234183414.13728.30.camel@blaa> In-Reply-To: <1234183414.13728.30.camel@blaa> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mark McLoughlin , qemu-devel@nongnu.org Mark McLoughlin wrote: > 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? > It's a good idea, but it may be hard to pull off practically speaking for the first release. Let's see how it works out. > - Will there be a release candidate? > Sometime this week, I'll try to post something summarizing our current state and anything outstanding. If there's time to put out an -rc, I'll try to make one available. Things may hiccup a bit. > - Is there any missing features that we might push out the release > date for? > Personally, I don't think so. I think openbios was the biggest issue because we don't have the code for the current firmware. It looks like that's been almost resolved. I'm more interested in getting a release out in a timely manner than holding up for any particular feature. If we have lots of features going in, I'd rather do more frequent releases than hold up releases. > - Post-release, is there any interest in maintaining a stable branch > until the next release? > I am tempted to try it out. Let's see how it goes. > - The plan for the next release is roughly 6 months, yes? > Yup. Regards, Anthony Liguori > Thanks, > Mark. > > > >