From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43265) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WW5Z8-00082J-Eo for qemu-devel@nongnu.org; Fri, 04 Apr 2014 10:58:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WW5Z4-0001AV-CB for qemu-devel@nongnu.org; Fri, 04 Apr 2014 10:57:58 -0400 Received: from mail-lb0-f175.google.com ([209.85.217.175]:42479) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WW5Z4-0001AR-5X for qemu-devel@nongnu.org; Fri, 04 Apr 2014 10:57:54 -0400 Received: by mail-lb0-f175.google.com with SMTP id w7so2580981lbi.34 for ; Fri, 04 Apr 2014 07:57:52 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20140403194940.15125.78389@loki> From: Peter Maydell Date: Fri, 4 Apr 2014 15:57:31 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 2.0.0-rc1 is now available List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Michael Roth , QEMU Developers On 4 April 2014 15:39, Stefan Hajnoczi wrote: > On Thu, Apr 3, 2014 at 10:02 PM, Peter Maydell wrote: >> On 3 April 2014 20:49, Michael Roth wrote: >>> Hello, >>> >>> On behalf of the QEMU Team, I'd like to announce the availability of the >>> second release candidate for the QEMU 2.0 release. This release is meant >>> for testing purposes and should not be used in a production environment. >>> >>> http://wiki.qemu.org/download/qemu-2.0.0-rc1.tar.bz2 >>> >>> You can help improve the quality of the QEMU 2.0 release by testing this >>> release and reporting bugs on Launchpad: >>> >>> https://bugs.launchpad.net/qemu/ >>> >>> The release plan for the 2.0 release is available at: >>> >>> http://wiki.qemu.org/Planning/2.0 >> >> We should probably update this -- we slipped a couple of days >> on the rc1, and I know there are still some fixes that will >> require an rc2. How about: >> rc2 7th or 8th April >> release 2 days after (assuming no fixes appear that need to >> go into an rc3) >> >> ? > > Sounds good. OK; I've updated the wiki page. Patches I know about for 2.0: [0/2] fix bugs involving linux-user signal handling [0/2] A15 board bugfixes dma-helpers: Initialize DMAAIOCB in_cancel flag target-i386: reorder fields in cpu/msr_hyperv_hypercall subsection Given the relatively small number and where we are in the release schedule I propose to just apply those directly to master. Is there anything else I should pick up? thanks -- PMM