From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <announce@edk2.groups.io>, <devel@edk2.groups.io>
Cc: "'Andrew Fish'" <afish@apple.com>,
"'Michael D Kinney'" <michael.d.kinney@intel.com>,
"'Demeter, Miki'" <miki.demeter@intel.com>,
"'Leif Lindholm'" <quic_llindhol@quicinc.com>
Subject: Soft Feature Freeze starts on 2023-05-08 for edk2-stable202305
Date: Tue, 9 May 2023 08:59:15 +0800 [thread overview]
Message-ID: <025701d98211$7a48da30$6eda8e90$@byosoft.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
Hi, all
We enter into Soft Feature Freeze phase on 2023-05-08. In this phase,
the feature under review will not be allowed to be pushed. The feature
passed review can still be merged.
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-stable202305 key words in the patch title and BZ, so the
community know this patch target and give the feedback.
To avoid the unnecessary changes to be merged in edk2 stable tag release,
all edk2 maintainers' write access will be temporarily disabled until stable
tag is released on 05-26. That means edk2 maintainer can't set push label in
pull request after 2023-05-08.
If the change wants to catch this stable tag 202305, please follow above
rules, then send the merge request to gaoliming@byosoft.com.cn or
michael.d.kinney@intel.com or miki.demeter@intel.com.
We will help merge the code change in soft feature freeze and hard feature
freeze phase.
Below is edk2-stable202305 tag planning Proposed Schedule
Date (00:00:00 UTC-8) Description
2023-02-24 Beginning of development
2023-05-08 Soft Feature Freeze
2023-05-12 Hard Feature Freeze
2023-05-26 Release
Thanks
Liming
[-- Attachment #2: Type: text/html, Size: 9165 bytes --]
reply other threads:[~2023-05-09 0: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='025701d98211$7a48da30$6eda8e90$@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