From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>
Cc: "Laszlo Ersek <lersek@redhat.com> (lersek@redhat.com)"
<lersek@redhat.com>,
"Andrew Fish (afish@apple.com)" <afish@apple.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: edk2-stable201905 features and soft/hard freeze and release date
Date: Thu, 23 May 2019 07:46:37 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E450083@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9D1BC3B@ORSMSX113.amr.corp.intel.com>
>-----Original Message-----
>From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>Michael D Kinney
>Sent: Thursday, May 23, 2019 10:08 AM
>To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>
>Cc: Laszlo Ersek <lersek@redhat.com> (lersek@redhat.com)
><lersek@redhat.com>; Andrew Fish (afish@apple.com) <afish@apple.com>;
>leif.lindholm@linaro.org; Cetola, Stephano <stephano.cetola@intel.com>
>Subject: [edk2-devel] edk2-stable201905 features and soft/hard freeze and
>release date
>
>Hello,
>
>There have been a few discussion during the soft freeze for
>edk2-stable201905 on changes that can be accepted or not.
>
>The TianoCore Stewards met today to discuss these topics and
>make some decisions on the following features.
>
>* Update OpenSSL version to upcoming 1.1.1
> https://bugzilla.tianocore.org/show_bug.cgi?id=1089
>
> This feature must be completed for edk2-stable201905.
> We are willing to extend the soft freeze, hard freeze,
> and release date to make sure this feature is completed.
> Please complete the patches and reviews and perform all
> validation required for this feature and provide status
> to the mailing list. The release date will be pushed out
> if required to accommodate this feature.
Mike:
Once the release is deferred, the release will happen June.
So, the stable tag will be changed to edk2-stable201906.
Wang, Jian and Ard:
I see you are working on this patch. Can you give the fix plan?
Then, I can propose new schedule on edk2-stable201905 tag.
Because the release is deferred, I will not send announcement for hard freeze this week.
>
>* Move network related components from MdeModulePkg to NetworkPkg
> https://bugzilla.tianocore.org/show_bug.cgi?id=1293
>
> Updating MdeModulePkg to remove the extra build of the network
> modules is considered low risk and should be completed for
> edk2-stable201905.
>
Thanks! So, I will push this patch soon.
>* Standardize EDK II PI root-of-trust verification implementation
> https://bugzilla.tianocore.org/show_bug.cgi?id=1617
>
> Move to edk-stable201908
>
>* FeatureFlagExpression Support in LibraryClasses section of INF file
> https://bugzilla.tianocore.org/show_bug.cgi?id=1446
>
> Move to edk-stable201908
>
>* Add new tool chain for LLVM/CLANG8.0
> https://bugzilla.tianocore.org/show_bug.cgi?id=1603
>
> Move to edk-stable201908
>
OK. I move these three features to next stable tag.
Thanks
Liming
>Please let us know if there are any other features that require
>consideration for edk2-stable201905.
>
>Of course critical bug fixes are accepted during the soft/hard
>freeze. If there is any doubt if a patch is a bug fix or a
>feature, please ask before doing any commits.
>
>Thanks,
>
>Mike
>
>
>
>
>
next prev parent reply other threads:[~2019-05-23 7:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 2:08 edk2-stable201905 features and soft/hard freeze and release date Michael D Kinney
2019-05-23 7:46 ` Liming Gao [this message]
2019-05-23 17:16 ` Leif Lindholm
2019-05-23 18:15 ` Michael D Kinney
2019-05-24 8:00 ` Liming Gao
2019-05-31 5:16 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E450083@SHSMSX104.ccr.corp.intel.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