From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:55230) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R7NF9-0002bL-D6 for qemu-devel@nongnu.org; Sat, 24 Sep 2011 04:05:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R7NF7-0002fV-D2 for qemu-devel@nongnu.org; Sat, 24 Sep 2011 04:05:51 -0400 Received: from mail-qy0-f180.google.com ([209.85.216.180]:64924) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R7NF7-0002fR-8f for qemu-devel@nongnu.org; Sat, 24 Sep 2011 04:05:49 -0400 Received: by qyc1 with SMTP id 1so4392537qyc.4 for ; Sat, 24 Sep 2011 01:05:48 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <4E7A828A.3030404@codemonkey.ws> References: <4E7A828A.3030404@codemonkey.ws> From: Blue Swirl Date: Sat, 24 Sep 2011 08:05:24 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori , Avi Kivity Cc: qemu-devel On Thu, Sep 22, 2011 at 12:34 AM, Anthony Liguori w= rote: > Consider this a friendly reminder that we're only three weeks away from t= he > soft feature freeze for 1.0. =C2=A0I've written a wiki page about my expe= ctations > for the soft feature freeze. =C2=A0It's inlined here for easier commentin= g. 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. > =3D=3D What is the soft feature freeze? =3D=3D > > The soft feature freeze is the beginning of the stabilization phase of > QEMU's development process. =C2=A0By the date of the soft feature freeze,= any > major feature should have some code posted to the qemu-devel mailing list= if > it's targeting a given release. > > =3D=3D What should I do by the soft feature freeze? =3D=3D > > For any major feature that you're targeting to the next release, you shou= ld: > > # Make sure that you've posted a patch series to qemu-devel > # Write a Feature page on the qemu.org wiki describing the feature and th= e > motivation > # On the release planning wiki page, link to your feature wiki page. > > =3D=3D Will my patches be rejected if I don't post before the soft featur= e > freeze? =3D=3D > > That's ultimately up to the subsystem maintainer. =C2=A0It's a value call= based > on the relative importance of the feature verses the disruptiveness of th= e > feature. =C2=A0It's always best to avoid this problem in the first place = and > release early, release > often[http://en.wikipedia.org/wiki/Release_early,_release_often]. > >