qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks


From: Avi Kivity
Subject: Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away)
Date: Sun, 25 Sep 2011 19:48:34 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20110906 Thunderbird/6.0.2

On 09/25/2011 07:36 PM, Blue Swirl wrote:
On Sun, Sep 25, 2011 at 2:10 PM, Avi Kivity<address@hidden>  wrote:
>  On 09/24/2011 11:05 AM, Blue Swirl wrote:
>>
>>  On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori<address@hidden>
>>    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.

Well, there's PPC VGA which is semi-broken by the incomplete conversion.

Please point out a test case and I'll try to fix it.

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]