From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Cc: "'Leif Lindholm'" <leif@nuviainc.com>,
"'Andrew Fish'" <afish@apple.com>,
"'Michael D Kinney'" <michael.d.kinney@intel.com>,
"'Demeter, Miki'" <miki.demeter@intel.com>
Subject: Hard Feature Freeze starts now for edk2-stable202208
Date: Mon, 15 Aug 2022 13:02:10 +0800 [thread overview]
Message-ID: <018e01d8b064$2d362150$87a263f0$@byosoft.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
Hi, all
Today, we enter into Hard Feature Freeze phase until edk2-stable202208 tag
is created at 2022-08-26. In this phase, there is no feature to be pushed.
The critical bug fix is still allowed.
If the patch is sent after Hard Feature Freeze, and plans to catch this
stable tag, please add edk2-stable202208 key words in the patch title and
BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.
Below is edk2-stable202208 tag planning
(https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planni
ng).
Date (00:00:00 UTC-8) Description
2022-05-27 Beginning of development
2022-08-08 Soft Feature Freeze
2022-08-12 Hard Feature Freeze
2022-08-26 Release
Thanks
Liming
[-- Attachment #2: Type: text/html, Size: 3220 bytes --]
reply other threads:[~2022-08-15 5:02 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='018e01d8b064$2d362150$87a263f0$@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