public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Andrew Fish" <afish@apple.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>, liming.gao@intel.com
Cc: "announce@edk2.groups.io" <announce@edk2.groups.io>,
	Laszlo Ersek <lersek@redhat.com>,
	Leif Lindholm <leif@nuviainc.com>,
	Mike Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202005
Date: Thu, 28 May 2020 20:05:59 -0700	[thread overview]
Message-ID: <444993E2-368C-47BF-A53A-629495C4AE95@apple.com> (raw)
In-Reply-To: <SN6PR11MB3197914CC799E155BE2216CA808F0@SN6PR11MB3197.namprd11.prod.outlook.com>

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

Liming,

Sounds good. There is a Stewards meeting next Tuesday so please let us know if there is any other feedback we could give that would be helpful. 

Thanks,

Andrew Fish

> On May 28, 2020, at 8:00 PM, Liming Gao <liming.gao@intel.com> wrote:
> 
> Stewards and all:
>   Leif requests two patches to catch this stable tag. They fix BZ https://bugzilla.tianocore.org/show_bug.cgi?id=2723 <https://bugzilla.tianocore.org/show_bug.cgi?id=2723>. I see the point that the linux distribution default GCC version may be 10 or above. Without this fix, those developers can’t pass build edk2-stable202005. So, Leif thinks this is a critical bug fix. But, today is the stable tag release date. To collect the more feedback, I suggest to delay this stable tag to the middle of next week (2020-06-03). Before you get the formal announcement of the stable tag release, please be patient in Hard Feature Freeze phase.
>
> https://edk2.groups.io/g/devel/message/60108 <https://edk2.groups.io/g/devel/message/60108> [PATCH] MdePkg/Include: AARCH64: disable outline atomics on GCC 10.2+
> https://edk2.groups.io/g/devel/message/59961 <https://edk2.groups.io/g/devel/message/59961> [PATCH v2] ArmPkg/CompilerIntrinsicsLib: provide atomics intrinsics
>
> Thanks
> Liming
> From: devel@edk2.groups.io <mailto:devel@edk2.groups.io> <devel@edk2.groups.io <mailto:devel@edk2.groups.io>> On Behalf Of Liming Gao
> Sent: 2020年5月22日 16:01
> To: devel@edk2.groups.io <mailto:devel@edk2.groups.io>; announce@edk2.groups.io <mailto:announce@edk2.groups.io>
> Cc: Laszlo Ersek <lersek@redhat.com <mailto:lersek@redhat.com>>; Leif Lindholm <leif@nuviainc.com <mailto:leif@nuviainc.com>>; afish@apple.com <mailto:afish@apple.com>; Kinney, Michael D <michael.d.kinney@intel.com <mailto:michael.d.kinney@intel.com>>
> Subject: [edk2-devel] Hard Feature Freeze starts now for edk2-stable202005
>
> 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: 12535 bytes --]

  reply	other threads:[~2020-05-29  3:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16114AE26AF23A6C.23490@groups.io>
2020-05-29  3:00 ` Hard Feature Freeze starts now for edk2-stable202005 Liming Gao
2020-05-29  3:05   ` Andrew Fish [this message]
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
     [not found]       ` <161471CADAA4F448.8494@groups.io>
2020-06-02  1:35         ` [edk2-announce] " Liming Gao
2020-06-02  1:53           ` Bret Barkelew
2020-06-02  2:37             ` [edk2-devel] " Liming Gao
2020-06-02  3:00               ` Bret Barkelew

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=444993E2-368C-47BF-A53A-629495C4AE95@apple.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