From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:53891) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WYGo6-0000N4-9g for qemu-devel@nongnu.org; Thu, 10 Apr 2014 11:22:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WYGo0-0001m9-1q for qemu-devel@nongnu.org; Thu, 10 Apr 2014 11:22:26 -0400 Received: from mx1.redhat.com ([209.132.183.28]:7618) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WYGnz-0001ly-Pa for qemu-devel@nongnu.org; Thu, 10 Apr 2014 11:22:19 -0400 Date: Thu, 10 Apr 2014 18:22:57 +0300 From: "Michael S. Tsirkin" Message-ID: <20140410152257.GE21110@redhat.com> References: <53467F83.4020508@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <53467F83.4020508@suse.de> Subject: Re: [Qemu-devel] Should we have a 2.0-rc3 ? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Peter Maydell , QEMU Developers , Michael Roth , Anthony Liguori , Paolo Bonzini , Andreas =?iso-8859-1?Q?F=E4rber?= On Thu, Apr 10, 2014 at 01:24:51PM +0200, Alexander Graf wrote: > > On 10.04.14 13:17, Peter Maydell wrote: > >So far I know of at least three fixes which should probably > >go into 2.0: > > * my fix for the configure stack-protector checks on MacOSX > > * MST's pull request updating the ACPI test blobs > > * MST says we need to update the hex files for ACPI too > > (otherwise you get a different ACPI blob depending on whether > > your build system had iasl or not, if I understand correctly) > > > >Are there any others? > > > >So we have two choices: > > > >(A) get those fixes into git today, and tag an rc3; that > >would then need some testing time and presumably we'd hope > >to tag it as the 2.0 release on Monday or Tuesday next week > > > >(B) say that the above are not worth fixing in 2.0 proper > >and plan to do a 2.0.1 in a few weeks with the above plus > >any other breakage that people find. > > > >Opinions? > > I think the best way forward is to do both. Do an rc3 with _only_ > those patches. Wait until Tuesday and do the final GA tag there. > > Then schedule a 2.0.1 in a few weeks. There will be bug fixes. > > And don't apply last-minute fixes from mst in the future :). > > > Alex Sorry about that. Though my last minute patches didn't actually break any stuff, they just weren't complete :) -- MST