From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Cc: "'Kinney, Michael D'" <michael.d.kinney@intel.com>,
"'Andrew Fish'" <afish@apple.com>,
"'Leif Lindholm'" <quic_llindhol@quicinc.com>
Subject: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202311
Date: Mon, 13 Nov 2023 22:57:05 +0800 [thread overview]
Message-ID: <001e01da1641$ab6836f0$0238a4d0$@byosoft.com.cn> (raw)
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Hi, all
Today, we enter into Hard Feature Freeze phase until edk2-stable202311 tag
is created at 2023-11-24. 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-stable202311 key words in the patch title and
BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.
Below is edk2-stable202311 tag planning.
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g
Date (00:00:00 UTC-8) Description
2023-08-25 Beginning of development
2023-11-06 Soft Feature Freeze
2023-11-10 Hard Feature Freeze
2023-11-24 Release
Thanks
Liming
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111157): https://edk2.groups.io/g/devel/message/111157
Mute This Topic: https://groups.io/mt/102562749/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: 5009 bytes --]
next reply other threads:[~2023-11-13 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 14:57 gaoliming via groups.io [this message]
2023-11-17 8:13 ` [edk2-devel] Hard Feature Freeze starts now for edk2-stable202311 Laszlo Ersek
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='001e01da1641$ab6836f0$0238a4d0$@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