From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Cc: <lersek@redhat.com>, <afish@apple.com>,
"'Leif Lindholm'" <leif@nuviainc.com>,
<michael.d.kinney@intel.com>,
"'Soumya K'" <soumya.k.guptha@intel.com>
Subject: Hard Feature Freeze starts now for edk2-stable202011
Date: Fri, 20 Nov 2020 16:05:41 +0800 [thread overview]
Message-ID: <018b01d6bf13$f0f28dc0$d2d7a940$@byosoft.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]
Hi, all
Today, we enter into Hard Feature Freeze phase until edk2-stable202011 tag
is created at 2020-11-27. In this phase, there is no feature to be pushed.
The critical bug fix is still allowed. So far, I know two security patches
need to catch this stable tag. They both passed code review before HFF. If
no objection, Laszlo will merge them for this stable tag.
https://edk2.groups.io/g/devel/message/67708 Security fix: possible heap
corruption with LzmaUefiDecompressGetInfo
https://edk2.groups.io/g/devel/message/67706 MdeModulePkg/Core/Dxe: limit
FwVol encapsulation section recursion
If the patch is sent after Hard Feature Freeze, and plans to catch this
stable tag, please add edk2-stable202011 key words in the patch title and
BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.
Below is edk2-stable202011 tag planning.
Date (00:00:00 UTC-8) Description
2020-09-04 Beginning of development
2020-11-06 Feature Planning Freeze
2020-11-13 Soft Feature Freeze
2020-11-20 Hard Feature Freeze
2020-11-27 Release
Thanks
Liming
[-- Attachment #2: Type: text/html, Size: 3890 bytes --]
reply other threads:[~2020-11-20 8:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='018b01d6bf13$f0f28dc0$d2d7a940$@byosoft.com.cn' \
--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