From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43197) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuKsa-00027O-SD for qemu-devel@nongnu.org; Thu, 05 Nov 2015 08:47:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZuKsW-00042o-Qp for qemu-devel@nongnu.org; Thu, 05 Nov 2015 08:47:04 -0500 Received: from e06smtp10.uk.ibm.com ([195.75.94.106]:46979) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZuKsW-00042j-Gs for qemu-devel@nongnu.org; Thu, 05 Nov 2015 08:47:00 -0500 Received: from localhost by e06smtp10.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 5 Nov 2015 13:46:59 -0000 Received: from b06cxnps4076.portsmouth.uk.ibm.com (d06relay13.portsmouth.uk.ibm.com [9.149.109.198]) by d06dlp02.portsmouth.uk.ibm.com (Postfix) with ESMTP id 53D6F2190056 for ; Thu, 5 Nov 2015 13:46:51 +0000 (GMT) Received: from d06av11.portsmouth.uk.ibm.com (d06av11.portsmouth.uk.ibm.com [9.149.37.252]) by b06cxnps4076.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id tA5DktD64194570 for ; Thu, 5 Nov 2015 13:46:55 GMT Received: from d06av11.portsmouth.uk.ibm.com (localhost [127.0.0.1]) by d06av11.portsmouth.uk.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id tA5Dksg2003236 for ; Thu, 5 Nov 2015 06:46:55 -0700 References: <1446725610.30393.23.camel@redhat.com> <563B586A.1060908@de.ibm.com> From: Christian Borntraeger Message-ID: <563B5DCE.3000106@de.ibm.com> Date: Thu, 5 Nov 2015 14:46:54 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] virtio-gpu doesn't build if you do a linux-headers update from kvm/next List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Paolo Bonzini , Gerd Hoffmann , QEMU Developers Am 05.11.2015 um 14:44 schrieb Peter Maydell: > On 5 November 2015 at 13:23, Christian Borntraeger > wrote: >> Maybe we should try to aim for a 3 month cadence for QEMU to reduce the >> pain of missing soft/hard freeze. -> maybe a topic for the next QEMU >> summit? > > We used to have 3 month releases, but I think we found that these > were too short: If you have about a month hardfreeze and a month > softfreeze then you only have a month of open feature development, > which seems pretty short to me. Yes, the overall process has to change for a 3 month cadence.