From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Cc: "'Andrew Fish'" <afish@apple.com>,
"'Kinney, Michael D'" <michael.d.kinney@intel.com>,
<leif.lindholm@oss.qualcomm.com>,
"'Ard Biesheuvel'" <ardb@kernel.org>
Subject: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202408
Date: Mon, 11 Nov 2024 21:14:51 +0800 [thread overview]
Message-ID: <01aa01db343b$b2911910$17b34b30$@byosoft.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Hi, all
Now, we enter into Hard Feature Freeze phase until edk2-stable202411 tag
is created at 2024-11-22. In this phase, there is no feature to be pushed.
The critical bug fix or the approved change is still allowed.
If the patch is sent after Hard Feature Freeze, and plans to catch this
stable tag, please add edk2-stable202411 key words in the patch title and
BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.
Below is edk2-stable202411 tag planning.
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g
Date (00:00:00 UTC-8) Description
2024-08-23 Beginning of development
2024-11-04 Soft Feature Freeze
2024-11-08 Hard Feature Freeze
2024-11-22 Release
Thanks
Liming
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120764): https://edk2.groups.io/g/devel/message/120764
Mute This Topic: https://groups.io/mt/109514144/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: text/html, Size: 4550 bytes --]
next reply other threads:[~2024-11-11 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 13:14 gaoliming via groups.io [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-10 1:31 [edk2-devel] Hard Feature Freeze starts now for edk2-stable202408 gaoliming via groups.io
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='01aa01db343b$b2911910$17b34b30$@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