From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] KVM call agenda for May, Tuesday 8th Date: Tue, 08 May 2012 09:24:42 -0500 Message-ID: <4FA92CAA.6070604@codemonkey.ws> References: <87pqag9psa.fsf@elfo.elfo> <4FA7C60E.8030802@codemonkey.ws> <4FA9296F.4060903@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: quintela@redhat.com, qemu-devel@nongnu.org, KVM devel mailing list , malc , Paolo Bonzini , Michael Roth , Blue Swirl To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Return-path: Received: from mail-yw0-f46.google.com ([209.85.213.46]:33320 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753815Ab2EHOYr (ORCPT ); Tue, 8 May 2012 10:24:47 -0400 Received: by yhmm54 with SMTP id m54so5362670yhm.19 for ; Tue, 08 May 2012 07:24:47 -0700 (PDT) In-Reply-To: <4FA9296F.4060903@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 05/08/2012 09:10 AM, Andreas F=E4rber wrote: > Am 07.05.2012 14:54, schrieb Anthony Liguori: >> On 05/07/2012 06:47 AM, Juan Quintela wrote: >>> >>> Please send in any agenda items you are interested in covering. >> >> - Status of the 1.1 release > > Since it looked like the call is not going to take place lacking > feedback from Anthony, I will provocatively go ahead and say the stat= us > of 1.1 is pretty bad, currently. ;) > > rc0 is available, but patches submitted for 1.1 shortly before rc0 > neither got review nor were applied. Neither did pulls or patches > applied by Anthony get such a notice fwiw so that it's hard to > distinguish what's missing for anyone but the patch author. All pulls got handled before -rc0 was tagged. > > With rc0 not being provided as tarball, it would be nice to document = the > official, reproducible way of packaging a QEMU tarball on the Wiki. I > have collected some steps from the Rob Landley mips thread, but the > submodules complicate things a bit. -rc0's are never provided as a tarball. This is how the release proces= s works=20 and someone always complains about it :-( > rc1 should've been released yesterday, but it's not available yet, no > info and same issue with patches not being applied. I missed a flight yesterday and spent the entire day at an airport so I= didn't=20 tag it yesterday. I'm going to work on it today. > In the current state of master, rc1 will not build on ppc due to an > #error introduced since rc0 by malc - with its history, Darwin/ppc > should not be a release blocker here and *some* fix to restore the bu= ild > should please be applied soon. So... what's the fix? Regards, Anthony Liguori > And worse, there's more and more colliding patch series on the list - > fixed-width visitors, realize, QBus, VMState, AREG0, CPU - for which = we > need a strategy to coordinate our ongoing development and post-1.1 > merging. Someone needs to rebase on someone else, question is whom. > > Some downstream feedback: I've so far been unable to do a static buil= d > of v1.1-rc0 in the openSUSE build system due to a -lpcre coming from > gthread-2.0.pc Libs.private - an issue we don't see for v1.0.1. If > another distro has encountered that issue I'd be grateful for feedbac= k. > Might be our own issue. > In course of investigating though, I've noticed that lots of our > configure checks are not limited to non-static/softmmu builds and wil= l > contribute cflags/libs to a static linux-user build even if unused. > > Regards, > Andreas >