From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36382) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgqM1-0001I2-8A for qemu-devel@nongnu.org; Mon, 05 Sep 2016 05:38:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bgqLw-0000uu-Vf for qemu-devel@nongnu.org; Mon, 05 Sep 2016 05:38:12 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42798) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bgqLw-0000uq-NH for qemu-devel@nongnu.org; Mon, 05 Sep 2016 05:38:08 -0400 Date: Mon, 5 Sep 2016 11:38:06 +0200 From: Kevin Wolf Message-ID: <20160905093806.GC4844@noname.redhat.com> References: <20160901140823.GA24262@stefanha-x1.localdomain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <20160901140823.GA24262@stefanha-x1.localdomain> Subject: Re: [Qemu-devel] proposed release timetable for 2.8 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Peter Maydell , QEMU Developers --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am 01.09.2016 um 16:08 hat Stefan Hajnoczi geschrieben: > On Thu, Sep 01, 2016 at 12:18:10PM +0100, Peter Maydell wrote: > > I know 2.7 isn't quite out the door yet, but I figured we should > > kick off the discussion of 2.8's schedule. At the QEMU Summit there > > was some discussion on how we're doing with releases, and I think > > the consensus view was that we should try to cut down the softfreeze > > period and also be stricter about (a) making sure pull requests get > > in in a timely way before rc0 and (b) we don't take new features > > during softfreeze. > >=20 > > (I'm not entirely sure I have those right, and in any case they're > > not pre-decided conclusions, so corrections and further opinion > > welcome.) > >=20 > > As a strawman, here's a timetable which results in a final > > release in December at the usual sort of time (ie allowing for > > the usual slippage without it hitting the holiday season): > >=20 > >=20 > > 2016-10-25 softfreeze, if you think we need 3 weeks, or: > > 2016-11-01 if you think we can do a 2 week softfreeze > > 2016-11-08 deadline for getting pull requests on list before hardfreeze? > > 2016-11-15 rc0 (start of hardfreeze) > > 2016-11-22 rc1 > > 2016-11-29 rc2 > > 2016-12-06 rc3 > > 2016-12-13 final v2.8.0 >=20 > I suggest we do the schedule above with a firm hardfreeze deadline where > no more feature pull requests are allowed. This means a 2 week > softfreeze and time before -rc0 for the maintainer to merge and test > pull requests: >=20 > 2016-10-25 softfreeze > 2016-11-08 hardfreeze > 2016-11-15 rc0 > 2016-11-22 rc1 > 2016-11-29 rc2 > 2016-12-06 rc3 > 2016-12-13 final v2.8.0 The major difference to the current process is here really that we don't do a -rc0 release any more. What you called -rc0 is really what used to be -rc1, i.e. a proper release candidate release where some testing and stabilisation has already happened. Though we'll probably not get quite as much testing as if we kept releasing an actual tarball as a hardfreeze snapshot (which is what -rc0 used to be rather than a proper release candidate.) Has -rc0 been particularly painful from a maintainer POV, or what is the reason for dropping it? Kevin --0F1p//8PRICkK4MW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJXzTz+AAoJEH8JsnLIjy/W6tkP/0V1y6NO2LGvb4MYDGVzlFaZ GHFQ38IBM8qG12qh7X/i5TJvUC8seG55ofyL/j4FF44WRP27ryy5IJJ8HQwuNS5I XdKe9rA/V/fAWBf7lQUarvgBQuIaqrf548EwMpog+7Qsn+3ghIa0ZQjDFDhUs3ao PCQxvmg35Ok0teusJFBAwBiCZoIlyOGmZ5+n94ZnLRkoWK0fu7gOY0bw30n6Olll sfiDt37W2Z+GTN3FisAd4ZsaMYzj1CJH9lnaDueC7Dc8a3bF19Ntrk0OydJEjzIr NqGNqbIAnDr6jZP0vXGZu0Qy951x6QI0R6AiEcoyZvqobckD4X/bgCyk2Uq9ZBQO 0V9r+etgwMGm52Kv5Cus6YMoTnXcPqLBNXaBSJEdFbmptV2rzCNcS6hDjak9sXMv fDBrLcFMNEKrpDkU9woOlc7o65o3FUlyCTehN9CawRtX4B+n6Nbhz9f5yXK/EIcL M0WHLczPCMmZje+MeOgWtnemWCHPFTP0zWdqIsalDeR89TIgd5olMYaja2FWILg4 jjjodNBggJZ/1OuhutwJlmpgLbUCKh9YukyRLm/rquOtIgxOR45v9GavMD+bTKZV /XlRtw4+u7JAFYA1J4LBkKuAYzHahvtfkjK7j/fXtUv91BaC8rDGkqUdjqLaS4OF AyM/Liey0xI/UV8bz8eJ =2BXF -----END PGP SIGNATURE----- --0F1p//8PRICkK4MW--