public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"announce@edk2.groups.io" <announce@edk2.groups.io>
Cc: "Andrew Fish (afish@apple.com)" <afish@apple.com>,
	Leif Lindholm <llindhol@qti.qualcomm.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Gao, Liming" <gaoliming@byosoft.com.cn>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202402
Date: Fri, 9 Feb 2024 22:34:48 +0000	[thread overview]
Message-ID: <CO1PR11MB4929145CED7D8E993ACE2B94D24B2@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)

Hi,

Today, we enter into Hard Feature Freeze phase until edk2-stable202402 tag
is created at 2024-02-23. 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-stable202402 key words in the patch title and
BZ, and also CC to Tianocore Stewards, then Stewards can give the comments.

Below is edk2-stable202402 tag planning.

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

Thanks,

Mike




-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115334): https://edk2.groups.io/g/devel/message/115334
Mute This Topic: https://groups.io/mt/104269392/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



             reply	other threads:[~2024-02-09 22:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 22:34 Michael D Kinney [this message]
2024-02-15  2:03 ` 回复: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202402 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=CO1PR11MB4929145CED7D8E993ACE2B94D24B2@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