From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lars Kurth Subject: Re: Xen 4.12 release planning Date: Wed, 25 Jul 2018 12:39:50 +0100 Message-ID: <29C1840E-1993-4A15-B724-908B8BDEDDD7@xenproject.org> References: <6a766b09-d5fe-a9ce-cacf-546c998ab803@suse.com> <0c25205b-b237-a7cd-aedf-45e7f86b3492@arm.com> <3563543c-c5c9-cb80-8d3e-c34e731118c8@suse.com> Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Content-Type: multipart/mixed; boundary="===============8406175124264256925==" Return-path: Received: from us1-rack-dfw2.inumbo.com ([104.130.134.6]) by lists.xenproject.org with esmtp (Exim 4.89) (envelope-from ) id 1fiI95-00073U-KY for xen-devel@lists.xenproject.org; Wed, 25 Jul 2018 11:39:55 +0000 Received: by mail-wr1-x42f.google.com with SMTP id a3-v6so7098660wrt.2 for ; Wed, 25 Jul 2018 04:39:53 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Sender: "Xen-devel" To: George Dunlap Cc: Juergen Gross , Andrew Cooper , Julien Grall , xen-devel List-Id: xen-devel@lists.xenproject.org --===============8406175124264256925== Content-Type: multipart/alternative; boundary="Apple-Mail=_6DD86429-DA1E-400F-860E-5DFC6B8255EC" --Apple-Mail=_6DD86429-DA1E-400F-860E-5DFC6B8255EC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On 25 Jul 2018, at 12:24, George Dunlap wrote: >=20 > On Wed, Jul 25, 2018 at 10:22 AM, Juergen Gross > wrote: >>=20 >> fFFFFFFR.......ffFFFFFFR.......ffFFFFFFR.......f >>=20 >> We can rule out several variants with release dates just before or in = a >> holiday season: >>=20 >> Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec >> Xx.XXXXX...xxxx...........xxXXXXx..............X holidays >> ffFFFFFFR.......ffFFFFFFR.......ffFFFFFFR....... >> .ffFFFFFFR.......ffFFFFFFR.......ffFFFFFFR...... >>=20 >> Best fit seems to be releasing in first half of March/July/November. = The >> main clash seems to be Chinese new year in the freeze period, but >> avoiding that would mean we'd have to either move into Christmas or >> Eastern, or to use a schedule with varying periods. >>=20 >> Please remember that Chinese new year is only 2 weeks long (at = varying >> dates) so only 2 weeks of the freeze period are hit. Next year the >> Chinese new year will be at February 5th. >>=20 >> For my 4.12 plan I've added some extra weeks between last posting = date >> and release date to accommodate for the holiday seasons, resulting in >> my suggestion. >=20 > Thanks for the detailed analysis Juregen. This seems good to me. >=20 > -George This looks good to me also. To address Julien's concerns, we could also = consider an earlier Last posting date/Hard code freeze date for Arm = related code to work around Julien's holiday plans. I think this would = be entirely OK and set expectations of contributors accordingly. But = maybe this is not necessary if Julien and Stefano can agree a work split = somehow.=20 Alternatively we could communicate absences of key reviewers say in = November to set expectations of contributors for the final stretch of = the release cycle. In other words, if a key reviewer is away, then = contributors will need to get series into good shape before their = reviewers go on vacation.=20 Regards Lars --Apple-Mail=_6DD86429-DA1E-400F-860E-5DFC6B8255EC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

On 25 Jul 2018, at 12:24, George Dunlap <dunlapg@umich.edu> = wrote:

On Wed, Jul = 25, 2018 at 10:22 AM, Juergen Gross <jgross@suse.com> = wrote:

fFFFFFFR.......ffFFFFFFR.......ffFFFFFFR.......f

We can rule out several variants with release = dates just before or in a
holiday season:

Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Xx.XXXXX...xxxx...........xxXXXXx..............X =      holidays
ffFFFFFFR.......ffFFFFFFR.......ffFFFFFFR.......
.ffFFFFFFR.......ffFFFFFFR.......ffFFFFFFR......

Best fit seems to be releasing in first half = of March/July/November. The
main clash seems to be Chinese = new year in the freeze period, but
avoiding that would = mean we'd have to either move into Christmas or
Eastern, = or to use a schedule with varying periods.

Please remember that Chinese new year is only 2 weeks long = (at varying
dates) so only 2 weeks of the freeze period = are hit. Next year the
Chinese new year will be at = February 5th.

For my 4.12 plan I've added = some extra weeks between last posting date
and release = date to accommodate for the holiday seasons, resulting in
my= suggestion.

Thanks for the detailed analysis Juregen.  This seems = good to me.

-George

This looks good to me also. To address Julien's = concerns, we could also consider an earlier Last posting date/Hard code = freeze date for Arm related code to work around Julien's holiday plans. = I think this would be entirely OK and set expectations of contributors = accordingly. But maybe this is not necessary if Julien and Stefano can = agree a work split somehow. 

Alternatively we could communicate absences of key = reviewers say in November to set expectations of contributors for the = final stretch of the release cycle. In other words, if a key reviewer is = away, then contributors will need to get series into good shape before = their reviewers go on vacation. 

Regards
Lars

= --Apple-Mail=_6DD86429-DA1E-400F-860E-5DFC6B8255EC-- --===============8406175124264256925== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVucHJvamVjdC5vcmcKaHR0cHM6Ly9saXN0 cy54ZW5wcm9qZWN0Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL3hlbi1kZXZlbA== --===============8406175124264256925==--