public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <announce@edk2.groups.io>
Cc: "'Andrew Fish'" <afish@apple.com>,
	"'Laszlo Ersek'" <lersek@redhat.com>, <leif@nuviainc.com>,
	"'Michael D Kinney'" <michael.d.kinney@intel.com>,
	"'Soumya Guptha'" <soumya.k.guptha@intel.com>
Subject: Soft Feature Freeze starts now for edk2-stable202102
Date: Mon, 22 Feb 2021 16:22:35 +0800	[thread overview]
Message-ID: <000201d708f3$df9c5a40$9ed50ec0$@byosoft.com.cn> (raw)

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

Hi, all

We will enter into Soft Feature Freeze phase. In this phase, the feature
under review will not be allowed to be merged. 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-stable202102 key words in the patch title and BZ, so the
community know this patch target and give the feedback.

 

Below is edk2-stable202102 tag planning
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g Proposed Schedule

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

2020-11-27  Beginning of development

2021-02-15  Feature Planning Freeze

2021-02-22  Soft Feature Freeze

2021-03-01  Hard Feature Freeze

2021-03-05  Release

 

Thanks

Liming


[-- Attachment #2: Type: text/html, Size: 3396 bytes --]

             reply	other threads:[~2021-02-22  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-22  8:22 gaoliming [this message]
2021-02-22 20:28 ` [edk2-devel] Soft Feature Freeze starts now for edk2-stable202102 PierreGondois
2021-02-23  0:55   ` 回复: " gaoliming

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='000201d708f3$df9c5a40$9ed50ec0$@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