From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: intel.com, ip: 134.134.136.65, mailfrom: liming.gao@intel.com) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by groups.io with SMTP; Mon, 03 Jun 2019 05:38:20 -0700 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jun 2019 05:38:19 -0700 X-ExtLoop1: 1 Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga004.jf.intel.com with ESMTP; 03 Jun 2019 05:38:19 -0700 Received: from fmsmsx163.amr.corp.intel.com (10.18.125.72) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 3 Jun 2019 05:38:18 -0700 Received: from shsmsx154.ccr.corp.intel.com (10.239.6.54) by fmsmsx163.amr.corp.intel.com (10.18.125.72) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 3 Jun 2019 05:38:18 -0700 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.137]) by SHSMSX154.ccr.corp.intel.com ([169.254.7.247]) with mapi id 14.03.0415.000; Mon, 3 Jun 2019 20:38:16 +0800 From: "Liming Gao" To: "devel@edk2.groups.io" , "lersek@redhat.com" CC: "leif.lindholm@linaro.org" , "afish@apple.com" , "Kinney, Michael D" , =?iso-8859-1?Q?Philippe_Mathieu-Daud=E9?= Subject: Re: [edk2-devel] Hard Feature Freeze starts now for edk2-stable201905 Thread-Topic: [edk2-devel] Hard Feature Freeze starts now for edk2-stable201905 Thread-Index: AdUZwQ5lYG110mFwTSG7MV3r19RszAAA9vCAABD2U8A= Date: Mon, 3 Jun 2019 12:38:16 +0000 Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4697AF@SHSMSX104.ccr.corp.intel.com> References: <4A89E2EF3DFEDB4C8BFDE51014F606A14E469154@SHSMSX104.ccr.corp.intel.com> <463d50e4-5bc6-648d-a8be-f2f1fb33e558@redhat.com> In-Reply-To: <463d50e4-5bc6-648d-a8be-f2f1fb33e558@redhat.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjJkYzc5YTgtZTZlYS00OGNiLTg3ZTQtMDljNjYwNGUyN2EyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiZ2x5VzZJRDNzMTdzYkZsWDVSUVc0bnhSNkd4SnVQZVNhRmtGbHdDT1p0dDMxVmdMa25JQjhEKzQ3RlkyU3F1MCJ9 dlp-product: dlpe-windows dlp-version: 11.0.600.7 dlp-reaction: no-action x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Return-Path: liming.gao@intel.com Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Laszlo: I agree this is a real functional bug fix. I am OK to add it for edk2-st= able201905. Thanks Liming > -----Original Message----- > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of La= szlo Ersek > Sent: Monday, June 3, 2019 8:29 PM > To: Gao, Liming ; devel@edk2.groups.io > Cc: leif.lindholm@linaro.org; afish@apple.com; Kinney, Michael D ; Philippe Mathieu-Daud=E9 > > Subject: Re: [edk2-devel] Hard Feature Freeze starts now for edk2-stable= 201905 >=20 > Hi, >=20 > On 06/03/19 06:02, Gao, Liming wrote: > > Hi, all > > Openssl1.1.1 update has been resolved. So, we enter into Hard Featur= e Freeze phase until edk2-stable201905 tag is created at > 2019-06-06. In this phase, there is no feature to be pushed. The bug fix= is still allowed. Below is the updated edk2-stable201905 tag > planning. > > > > Date (00:00:00 UTC-8) Description > > 2018-03-08 (12PM) Beginning of development > > 2019-05-17 Soft Feature Freeze > > 2019-06-03 Hard Feature Freeze > > 2019-06-06 Release >=20 > I'd like to push the series for > . It's a regressi= on > fix. >=20 > The series -- linked from comment 1 on the bug -- was reviewed on 29 May > 2019: >=20 > http://mid.mail-archive.com/20190529151209.17503-1-lersek@redhat.com > https://edk2.groups.io/g/devel/message/41624 >=20 > Normally I'd just push this series, but Mike mentioned last time that I > needed to show "criticality". I think the regression has fairly > impactful symptoms; please see comment 2 on the bug. >=20 > I plan to advance the ArmVirtQemu and OVMF firmware binaries that are to > be bundled with QEMU 4.1 to edk2-stable201905, and fixing this > regression would be helpful. (Otherwise QEMU 4.1 will stick with the > currently bundled edk2-stable201903 version.) >=20 > Thanks! > Laszlo >=20 >=20