From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Cc: "'Andrew \(EFI\) Fish'" <afish@apple.com>,
"'Laszlo Ersek'" <lersek@redhat.com>,
"'Leif Lindholm'" <leif@nuviainc.com>,
"'Michael D Kinney'" <michael.d.kinney@intel.com>,
"'Guptha, Soumya K'" <soumya.k.guptha@intel.com>,
"'Pandya, Puja'" <puja.pandya@intel.com>,
"'Brijesh Singh'" <brijesh.singh@amd.com>,
"'Etienne Carriere'" <etienne.carriere@linaro.org>
Subject: Soft Feature Freeze will start on 2021-05-17 for edk2-stable202105
Date: Fri, 14 May 2021 10:59:20 +0800 [thread overview]
Message-ID: <023001d7486d$23117220$69345660$@byosoft.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
Hi, all
We will enter into Soft Feature Freeze phase on 2021-05-17. In this phase,
the feature under review will not be allowed to be pushed. The feature
passed review can still be merged. Now, most planning features have been
merged.
If the feature plans to catch this stable tag, please make sure it pass code
review before 2021-05-17.
The patch review can continue without break in edk2 community. If the patch
is sent before Soft Feature Freeze, and plans to catch this stable tag, the
patch contributor need reply to his patch and notify edk2 community. If the
patch is sent after Soft Feature Freeze, and plans to catch this stable tag,
please add edk2-stable202105 key words in the patch title and BZ, so the
community know this patch target and give the feedback.
Below is edk2-stable202105 tag planning
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g Proposed Schedule
Date (00:00:00 UTC-8) Description
2021-03-05 Beginning of development
2021-05-10 Feature Planning Freeze
2021-05-17 Soft Feature Freeze
2021-05-24 Hard Feature Freeze
2021-05-28 Release
Thanks
Liming
[-- Attachment #2: Type: text/html, Size: 3818 bytes --]
reply other threads:[~2021-05-14 2:59 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='023001d7486d$23117220$69345660$@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