From: "Laszlo Ersek" <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"afish@apple.com" <afish@apple.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: Hard Feature Freeze starts now for edk2-stable201905
Date: Mon, 3 Jun 2019 14:29:21 +0200 [thread overview]
Message-ID: <463d50e4-5bc6-648d-a8be-f2f1fb33e558@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E469154@SHSMSX104.ccr.corp.intel.com>
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
<https://bugzilla.tianocore.org/show_bug.cgi?id=1859>. 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
next prev parent reply other threads:[~2019-06-03 12:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 4:02 Hard Feature Freeze starts now for edk2-stable201905 Liming Gao
2019-06-03 12:29 ` Laszlo Ersek [this message]
2019-06-03 12:38 ` [edk2-devel] " Liming Gao
2019-06-03 17:06 ` Laszlo Ersek
2019-06-04 20:29 ` Michael D Kinney
2019-06-04 21:20 ` [edk2-devel] " Wang, Jian J
2019-06-05 0:00 ` Liming Gao
[not found] ` <15A524651DAE72A1.22095@groups.io>
2019-06-05 8:03 ` Liming Gao
[not found] ` <15A53EB5F1DA28B3.17041@groups.io>
2019-06-06 4:46 ` Liming Gao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=463d50e4-5bc6-648d-a8be-f2f1fb33e558@redhat.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox