From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "gaoliming@byosoft.com.cn" <gaoliming@byosoft.com.cn>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"announce@edk2.groups.io" <announce@edk2.groups.io>
Cc: 'Andrew Fish' <afish@apple.com>,
'Leif Lindholm' <quic_llindhol@quicinc.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-announce] Soft Feature Freeze will start on Feb 5th for edk2-stable202402
Date: Thu, 8 Feb 2024 16:36:03 +0000 [thread overview]
Message-ID: <CO1PR11MB49299C7C4AFF32E280DAB47ED2442@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <024c01da5765$f728ca90$e57a5fb0$@byosoft.com.cn>
Hello,
Just a reminder we are in a Soft Freeze and will enter Hard Freeze
on 2-9-2024.
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
If there are any patches that started review before the soft freeze and
and have completed review and have not been merged, please respond to this
thread with the details so those can be merged before entering hard freeze.
If there are any changes that were sent during the soft freeze and must
be merged for the edk2-stable202402 release, then please make sure the
patch emails have [edk2-stable202402] in the subject line so those can
be reviewed by the stewards.
Thanks,
Mike
> -----Original Message-----
> From: announce@edk2.groups.io <announce@edk2.groups.io> On Behalf Of
> gaoliming via groups.io
> Sent: Sunday, February 4, 2024 4:31 AM
> 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-announce] Soft Feature Freeze will start on Feb 5th for
> edk2-stable202402
>
> Hi, all
>
>
>
> We will enter into Soft Feature Freeze phase soon. 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-stable202402 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 02-23. That means edk2 maintainer can't set push
> label in
>
> pull request after soft feature freeze starts.
>
>
>
> If the change wants to catch this stable tag 202402, please follow
> above
>
> rules, then send the merge request to gaoliming@byosoft.com.cn
> <mailto:gaoliming@byosoft.com.cn> or
>
> michael.d.kinney@intel.com <mailto:michael.d.kinney@intel.com> .
>
>
>
> We will help merge the code change in soft feature freeze and hard
> feature
>
> freeze phase.
>
>
>
> Below is edk2-stable202402 tag planning Proposed Schedule
>
> Date (00:00:00 UTC-8) Description
>
>
>
> 2023-11-24 Beginning of development
>
> 2024-02-05 Soft Feature Freeze
>
> 2024-02-09 Hard Feature Freeze
>
> 2024-02-23 Release
>
>
>
> Thanks
>
> Liming
>
>
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115269): https://edk2.groups.io/g/devel/message/115269
Mute This Topic: https://groups.io/mt/104241956/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-02-08 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 12:30 [edk2-devel] Soft Feature Freeze will start on Feb 5th for edk2-stable202402 gaoliming via groups.io
2024-02-08 16:36 ` Michael D Kinney [this message]
2024-02-09 10:31 ` [edk2-devel] [edk2-announce] " Jayaprakash, N
2024-02-09 17:08 ` Michael D Kinney
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=CO1PR11MB49299C7C4AFF32E280DAB47ED2442@CO1PR11MB4929.namprd11.prod.outlook.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