public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	"announce@edk2.groups.io" <announce@edk2.groups.io>
Cc: Laszlo Ersek <lersek@redhat.com>,
	Leif Lindholm <leif@nuviainc.com>,
	"afish@apple.com" <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Hard Feature Freeze starts now for edk2-stable202005
Date: Fri, 22 May 2020 08:01:16 +0000	[thread overview]
Message-ID: <SN6PR11MB3197FC887F4BF880C5A0E33F80B40@SN6PR11MB3197.namprd11.prod.outlook.com> (raw)

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

Hi, all
  Today, we enter into Hard Feature Freeze phase until edk2-stable202005 tag is created at 2020-05-29. In this phase, there is no feature to be pushed. The critical bug fix is still allowed.

  If the patch is sent after Hard Feature Freeze, and plans to catch this stable tag, please add edk2-stable202005 key words in the patch title and BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.

Below is edk2-stable202005 tag planning.
Date (00:00:00 UTC-8) Description
2020-03-04      Beginning of development
2020-05-08      Feature Planning Freeze
2020-05-15      Soft Feature Freeze
2020-05-22      Hard Feature Freeze
2020-05-29      Release

Thanks
Liming


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

             reply	other threads:[~2020-05-22  8:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22  8:01 Liming Gao [this message]
2020-05-22 15:11 ` Hard Feature Freeze starts now for edk2-stable202005 Bret Barkelew
2020-05-25 17:46   ` Laszlo Ersek
2020-05-26 22:11     ` [EXTERNAL] " Bret Barkelew
2020-05-27  2:21       ` Liming Gao
2020-05-27  2:25         ` [edk2-devel] " Bret Barkelew
2020-05-27 13:08       ` Laszlo Ersek
     [not found] <16114AE26AF23A6C.23490@groups.io>
2020-05-29  3:00 ` Liming Gao
2020-05-29  3:06   ` Michael D Kinney
2020-05-29 11:59     ` Laszlo Ersek
2020-05-29 11:58   ` Laszlo Ersek
2020-05-30 16:25   ` Liming Gao
2020-05-30 17:16     ` Bret Barkelew
2020-06-01 14:28       ` Liming Gao

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=SN6PR11MB3197FC887F4BF880C5A0E33F80B40@SN6PR11MB3197.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