public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Cc: "'Michael D Kinney'" <michael.d.kinney@intel.com>,
	"'Andrew Fish'" <afish@apple.com>,
	"'Leif Lindholm'" <quic_llindhol@quicinc.com>
Subject: [edk2-devel] Soft Feature Freeze starts now for edk2-stable202408
Date: Tue, 6 Aug 2024 09:11:55 +0800	[thread overview]
Message-ID: <018e01dae79d$a2779a80$e766cf80$@byosoft.com.cn> (raw)

[-- Attachment #1: Type: text/plain, Size: 1924 bytes --]

Hi, all

 

  We enter into Soft Feature Freeze phase now. 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 under review process, and plans to catch this stable tag, the

patch contributor need to send the request in edk2 mail list. If the patch 

is submitted after Soft Feature Freeze, and plans to catch this stable tag,

Please send the request in edk2 mail list and notify edk2 community, 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 08-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 202408, please follow above

rules, then send the pull 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-stable202408 tag planning Proposed Schedule

Date (00:00:00 UTC-8) Description

2024-05-24 Beginning of development

2024-08-05 Soft Feature Freeze

2024-08-09 Hard Feature Freeze

2024-08-23 Release

 

Thanks

Liming

 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120245): https://edk2.groups.io/g/devel/message/120245
Mute This Topic: https://groups.io/mt/107744100/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: 9935 bytes --]

                 reply	other threads:[~2024-08-06  1:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='018e01dae79d$a2779a80$e766cf80$@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