From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn
Cc: "'Kinney, Michael D'" <michael.d.kinney@intel.com>,
'Andrew Fish' <afish@apple.com>,
'Leif Lindholm' <quic_llindhol@quicinc.com>
Subject: Re: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202311
Date: Fri, 17 Nov 2023 09:13:58 +0100 [thread overview]
Message-ID: <ee43a5a6-361e-8678-cb0c-22d04a847c80@redhat.com> (raw)
In-Reply-To: <001e01da1641$ab6836f0$0238a4d0$@byosoft.com.cn>
(-announce)
On 11/13/23 15:57, gaoliming via groups.io wrote:
> 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-Planning <https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning>
I've refreshed the bugfix/feature list up to edk2 commit 3db76e6476e4
(wiki commit bbcacb2a60d7).
If something is missing, please let me know.
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111338): https://edk2.groups.io/g/devel/message/111338
Mute This Topic: https://groups.io/mt/102562749/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2023-11-17 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 14:57 [edk2-devel] Hard Feature Freeze starts now for edk2-stable202311 gaoliming via groups.io
2023-11-17 8:13 ` Laszlo Ersek [this message]
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=ee43a5a6-361e-8678-cb0c-22d04a847c80@redhat.com \
--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