From: "Leif Lindholm" <leif@nuviainc.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn
Cc: announce@edk2.groups.io, "'Kinney,
Michael D'" <michael.d.kinney@intel.com>,
'Laszlo Ersek' <lersek@redhat.com>,
'Andrew Fish' <afish@apple.com>,
'Soumya Guptha' <soumya.k.guptha@intel.com>
Subject: Re: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202102
Date: Mon, 1 Mar 2021 13:24:23 +0000 [thread overview]
Message-ID: <20210301132423.GS1664@vanye> (raw)
In-Reply-To: <001d01d70e73$18a6c710$49f45530$@byosoft.com.cn>
On Mon, Mar 01, 2021 at 16:15:51 +0800, gaoliming wrote:
> Hi, all
>
> Today, we enter into Hard Feature Freeze phase until edk2-stable202102 tag
> is created at 2021-03-05. In this phase, there is no feature to be pushed.
> The critical bug fix is still allowed. So far, there are two patches to
> catch this stable tag. They both passed code review before HFF. If no
> objection, they will be merged for this stable tag.
>
>
>
> 1. Fix two issue in ArmGicLib
> (https://edk2.groups.io/g/devel/message/72175)
I just pushed this fix, and closed the associated BZ.
/
Leif
> 2. Fix CET shadow stack token busy bit clear issue
> (https://edk2.groups.io/g/devel/message/71864)
>
>
>
> If the patch is sent after Hard Feature Freeze, and plans to catch this
> stable tag, please add edk2-stable202102 key words in the patch title and
> BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.
>
>
>
> Below is edk2-stable202102 tag planning.
>
> Date (00:00:00 UTC-8) Description
>
> 2020-11-27 Beginning of development
>
> 2021-02-15 Feature Planning Freeze
>
> 2021-02-22 Soft Feature Freeze
>
> 2021-03-01 Hard Feature Freeze
>
> 2021-03-05 Release
>
>
>
> Thanks
>
> Liming
>
>
>
>
>
>
prev parent reply other threads:[~2021-03-01 13:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:15 Hard Feature Freeze starts now for edk2-stable202102 gaoliming
2021-03-01 13:24 ` Leif Lindholm [this message]
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=20210301132423.GS1664@vanye \
--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