From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: redhat.com, ip: 209.132.183.28, mailfrom: lersek@redhat.com) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by groups.io with SMTP; Mon, 03 Jun 2019 05:29:42 -0700 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6AD243082E72; Mon, 3 Jun 2019 12:29:26 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-121-13.rdu2.redhat.com [10.10.121.13]) by smtp.corp.redhat.com (Postfix) with ESMTP id DAB5A605AE; Mon, 3 Jun 2019 12:29:22 +0000 (UTC) Subject: Re: Hard Feature Freeze starts now for edk2-stable201905 To: "Gao, Liming" , "devel@edk2.groups.io" Cc: "leif.lindholm@linaro.org" , "afish@apple.com" , "Kinney, Michael D" , =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= References: <4A89E2EF3DFEDB4C8BFDE51014F606A14E469154@SHSMSX104.ccr.corp.intel.com> From: "Laszlo Ersek" Message-ID: <463d50e4-5bc6-648d-a8be-f2f1fb33e558@redhat.com> Date: Mon, 3 Jun 2019 14:29:21 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E469154@SHSMSX104.ccr.corp.intel.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.46]); Mon, 03 Jun 2019 12:29:26 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Hi, On 06/03/19 06:02, Gao, Liming wrote: > Hi, all > Openssl1.1.1 update has been resolved. So, we enter into Hard Feature 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 I'd like to push the series for . It's a regression fix. The series -- linked from comment 1 on the bug -- was reviewed on 29 May 2019: http://mid.mail-archive.com/20190529151209.17503-1-lersek@redhat.com https://edk2.groups.io/g/devel/message/41624 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. 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.) Thanks! Laszlo