public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming via groups.io" <gaoliming=byosoft.com.cn@groups.io>
To: "'Andrew Fish'" <afish@apple.com>,
	"'Leif Lindholm'" <quic_llindhol@quicinc.com>,
	"'Kinney, Michael D'" <michael.d.kinney@intel.com>,
	"'Demeter, Miki'" <miki.demeter@intel.com>
Cc: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Subject: [edk2-devel] Soft Feature Freeze starts now for edk2-stable202308
Date: Tue, 8 Aug 2023 16:28:54 +0800	[thread overview]
Message-ID: <006301d9c9d2$5ea7f140$1bf7d3c0$@byosoft.com.cn> (raw)

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

Hi, all

 

  We enter into Soft Feature Freeze phase today. 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-stable202308 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 08-25. That means edk2 maintainer can't set push label in

pull request after today. 

 

  If the change wants to catch this stable tag 202308, please follow above

rules, then send the merge request to gaoliming@byosoft.com.cn or 

michael.d.kinney@intel.com or miki.demeter@intel.com.

 

  We will help merge the code change in soft feature freeze and hard feature

freeze phase. 

 

Below is edk2-stable202308 tag planning Proposed Schedule

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

2023-05-26  Beginning of development

2023-08-07  Soft Feature Freeze

2023-08-11  Hard Feature Freeze

2023-08-25  Release

 

Thanks

Liming

 

 



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

             reply	other threads:[~2023-08-08  8:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  8:28 gaoliming via groups.io [this message]
2023-08-08  8:31 ` [edk2-devel] Soft Feature Freeze starts now for edk2-stable202308 Ard Biesheuvel
2023-08-08  8:46   ` 回复: " 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='006301d9c9d2$5ea7f140$1bf7d3c0$@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