Makes sense!

Do we intend/agree to apply this rule on all new features or big changes (though practically how we gate the granularity of changes?)?

Regards,

Yong

From: "Rowsell, Brent" <Brent.Rowsell@windriver.com>
Date: Friday, 6 July 2018 at 8:58 AM
To: "Hu, Yong" <yong.hu@intel.com>, "Young, Ken" <Ken.Young@windriver.com>, "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>
Subject: RE: [Starlingx-discuss] [stx-tools] New Kernel Version

Going forward, I would recommend pending upgrades be posted to the mailing list before the reviews are actually submitted.

Brent

From: Hu, Yong [mailto:yong.hu@intel.com]
Sent: Thursday, July 5, 2018 8:56 PM
To: Young, Ken <Ken.Young@windriver.com>; starlingx-discuss@lists.starlingx.io
Subject: Re: [Starlingx-discuss] [stx-tools] New Kernel Version

Hi Ken,

We might need a sync-up on this kernel upgrade topic.

Actually, moving forward, I would suggest, if there are any big changes to come, we both sides need to inform each other in advance, to avoid duplications or conflicts.

Regards,

Yong

From: "Young, Ken" <Ken.Young@windriver.com>
Date: Friday, 6 July 2018 at 12:21 AM
To: "starlingx-discuss@lists.starlingx.io" <starlingx-discuss@lists.starlingx.io>
Subject: [Starlingx-discuss] [stx-tools] New Kernel Version

I discovered 2 new reviews this morning which are security related this morning:

https://review.openstack.org/#/c/580287/

https://review.openstack.org/#/c/580308/

These reviews propose to merge the latest CentOS kernel 862.6.3 to address the latest Spectre / Meltdown CVEs.

Before this is completed, we have a kernel update to 862.3.2 we would like to merge which includes module updates to enable containers which we would like to get in first.  Otherwise, this will generate a significant amount of rework for these submissions.  The easiest path is to follow the kernels in order.

We will work to get our updated kernel in ASAP.

Thank you in advance.

Regards,

Ken Y