From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LUTQF-0006F1-QI for qemu-devel@nongnu.org; Tue, 03 Feb 2009 17:07:11 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LUTQE-0006E8-AO for qemu-devel@nongnu.org; Tue, 03 Feb 2009 17:07:11 -0500 Received: from [199.232.76.173] (port=36872 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LUTQE-0006Dv-0w for qemu-devel@nongnu.org; Tue, 03 Feb 2009 17:07:10 -0500 Received: from mx1.redhat.com ([66.187.233.31]:33607) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LUTQD-00047H-JV for qemu-devel@nongnu.org; Tue, 03 Feb 2009 17:07:09 -0500 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n13M782g019566 for ; Tue, 3 Feb 2009 17:07:08 -0500 Received: from file.fab.redhat.com (file.fab.redhat.com [10.33.63.6]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n13M79Ou007703 for ; Tue, 3 Feb 2009 17:07:10 -0500 Received: from file.fab.redhat.com (localhost.localdomain [127.0.0.1]) by file.fab.redhat.com (8.13.1/8.13.1) with ESMTP id n13M773j018146 for ; Tue, 3 Feb 2009 22:07:07 GMT Received: (from berrange@localhost) by file.fab.redhat.com (8.13.1/8.13.1/Submit) id n13M77t9018120 for qemu-devel@nongnu.org; Tue, 3 Feb 2009 22:07:07 GMT Date: Tue, 3 Feb 2009 22:07:07 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Cutting a new QEMU release Message-ID: <20090203220707.GD9735@redhat.com> References: <4988AD96.6090308@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4988AD96.6090308@codemonkey.ws> Reply-To: "Daniel P. Berrange" , 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, Feb 03, 2009 at 02:48:22PM -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. I'd like to see a new release if at all practical. For Fedora there is a push to ship KVM and QEMU packages based off the same source tree to make patching security flaws more pratical. Given that KVM ships off a QEMU SVN snapshot, having a single source tree would mean shipping our full multi-arch QEMU package off a SVN snapshot too. I don't find this a particularly appealing thing - if CVS snapshot is stable enough for it to be exposed to Fedora users, I'd like to think QEMU developers would be happy with a official release. If the QEMU dev community considers the code too unstable to release, then exposing it to Fedora users seem sub-optimal. Personally I test & use the i386 and x86_64 system emulator parts of QEMU, and those seem generally stable enough to base a new release off. So I'd welcome a new release from that POV. I'll leave others to comment on quality of the other arch targets. > 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. A QEMU release by the end of the month would work pretty well for the time scale we're working on to get stuff into the Fedora 11 release too. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|