From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:33657)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R7pQ7-0003dr-00
	for qemu-devel@nongnu.org; Sun, 25 Sep 2011 10:11:03 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R7pQ5-0002TD-QP
	for qemu-devel@nongnu.org; Sun, 25 Sep 2011 10:11:02 -0400
Received: from mx1.redhat.com ([209.132.183.28]:21204)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1R7pQ5-0002T9-G4
	for qemu-devel@nongnu.org; Sun, 25 Sep 2011 10:11:01 -0400
Message-ID: <4E7F366F.9060501@redhat.com>
Date: Sun, 25 Sep 2011 17:10:55 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4E7A828A.3030404@codemonkey.ws>
	<CAAu8pHs7uMeusg1PoMkDrxew6WzOaSGJJJgtbDAwwwKwYeGx_Q@mail.gmail.com>
In-Reply-To: <CAAu8pHs7uMeusg1PoMkDrxew6WzOaSGJJJgtbDAwwwKwYeGx_Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three
 weeks away)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>

On 09/24/2011 11:05 AM, Blue Swirl wrote:
> On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori<anthony@codemonkey.ws>  wrote:
> >  Consider this a friendly reminder that we're only three weeks away from the
> >  soft feature freeze for 1.0.  I've written a wiki page about my expectations
> >  for the soft feature freeze.  It's inlined here for easier commenting.
>
> I think the freezes and the release should be delayed until the memory
> API conversion is finished, deliberately shipping semi-broken code
> just to satisfy schedules does not benefit anyone but the schedule
> creator. It looks to me that converting all buses and devices might be
> finished by the deadline but it may as well take a bit more until
> everything works again.
>

There is a difference between "incomplete conversion" and "semi-broken 
code".  Any breakage should be fixed promptly, but after some freeze 
date (not sure if this is the one proposed), additional conversions 
would be pushed to 1.1.

-- 
error compiling committee.c: too many arguments to function