[Top][All Lists]

[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: Anthony Liguori
Subject: Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away)
Date: Sun, 25 Sep 2011 14:50:52 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10

On 09/25/2011 09:10 AM, Avi Kivity 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.

Right, it's up to the sub maintainers to determine whether something should be delayed once we're in soft feature freeze.

The dates are:

10/15 - Soft Feature Freeze
11/01 - Hard Freeze
11/01 - qemu-1.0-rc0 is tagged
11/04 - qemu-1.0-rc1 is tagged and released
11/11 - qemu-1.0-rc2 is tagged and released
11/18 - qemu-1.0-rc3 is tagged and released
11/23 - qemu-1.0-rc4 is tagged and released
12/01 - qemu-1.0 is tagged and released

Since there's a solid month of hard freeze, I would think that that's more than enough time to stablize memory API changes.


Anthony Liguori

reply via email to

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