From: "Liming Gao" <liming.gao@intel.com>
To: "Wang, Jian J" <jian.j.wang@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"Laszlo Ersek (lersek@redhat.com)" <lersek@redhat.com>,
"afish@apple.com" <afish@apple.com>
Subject: Re: [edk2-devel] Hard Feature Freeze starts now for edk2-stable201905
Date: Wed, 5 Jun 2019 00:00:58 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E46BC99@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <D827630B58408649ACB04F44C510003625910702@SHSMSX107.ccr.corp.intel.com>
Another one is to fix Maintainers.txt.
[edk2-devel] [Patch] Maintainers.txt: Remove Network maintainers for MdeModulePkg/Universal/Network
>-----Original Message-----
>From: Wang, Jian J
>Sent: Wednesday, June 05, 2019 5:21 AM
>To: devel@edk2.groups.io; Kinney, Michael D <michael.d.kinney@intel.com>;
>Gao, Liming <liming.gao@intel.com>
>Cc: leif.lindholm@linaro.org; Laszlo Ersek (lersek@redhat.com)
><lersek@redhat.com>; afish@apple.com
>Subject: RE: [edk2-devel] Hard Feature Freeze starts now for edk2-
>stable201905
>
>There's a fix for build failure.
>
>*[edk2-devel] [PATCH] CryptoPkg/OpensslLib: fix VS2017 build failure
>
>Regards,
>Jian
>
>
>> -----Original Message-----
>> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
>> Michael D Kinney
>> Sent: Wednesday, June 05, 2019 4:29 AM
>> To: Gao, Liming <liming.gao@intel.com>; devel@edk2.groups.io; Kinney,
>> Michael D <michael.d.kinney@intel.com>
>> Cc: leif.lindholm@linaro.org; Laszlo Ersek (lersek@redhat.com)
>> <lersek@redhat.com>; afish@apple.com
>> Subject: Re: [edk2-devel] Hard Feature Freeze starts now for edk2-
>stable201905
>>
>> Hello,
>>
>> The patches for edk2-stable201905 were reviewed this morning.
>> The following 2 patches are in scope for the hard freeze.
>>
>> * [edk2-devel] [PATCH for-edk2-stable201905] Revert "EmulatorPkg: don't
>> display the cpu current speed"
>> * [edk2-devel] [Patch V2] edk2: Update additional licenses in Readme.md
>>
>> Please reply to this email if there are any additional patches or
>> issues that must be resolved in the hard freeze for this release.
>>
>> We are still targeting the release for 2019-06-06.
>>
>> Thanks,
>>
>> Mike
>>
>> ======
>>
>>
>> From: Gao, Liming
>> Sent: Sunday, June 2, 2019 9:02 PM
>> To: devel@edk2.groups.io
>> Cc: leif.lindholm@linaro.org; Laszlo Ersek (lersek@redhat.com)
>> <lersek@redhat.com>; afish@apple.com; Kinney, Michael D
>> <michael.d.kinney@intel.com>
>> Subject: Hard Feature Freeze starts now for edk2-stable201905
>>
>> Hi, all
>> Openssl1.1.1 update has been resolved. So, we enter into Hard Feature
>Freeze
>> phase until edk2-stable201905 tag is created at 2019-06-06. In this phase,
>there
>> is no feature to be pushed. The bug fix is still allowed. Below is the updated
>> edk2-stable201905 tag planning.
>>
>> Date (00:00:00 UTC-8) Description
>> 2018-03-08 (12PM) Beginning of development
>> 2019-05-17 Soft Feature Freeze
>> 2019-06-03 Hard Feature Freeze
>> 2019-06-06 Release
>>
>> Thanks
>> Liming
>>
>>
next prev parent reply other threads:[~2019-06-05 0:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 4:02 Hard Feature Freeze starts now for edk2-stable201905 Liming Gao
2019-06-03 12:29 ` Laszlo Ersek
2019-06-03 12:38 ` [edk2-devel] " Liming Gao
2019-06-03 17:06 ` Laszlo Ersek
2019-06-04 20:29 ` Michael D Kinney
2019-06-04 21:20 ` [edk2-devel] " Wang, Jian J
2019-06-05 0:00 ` Liming Gao [this message]
[not found] ` <15A524651DAE72A1.22095@groups.io>
2019-06-05 8:03 ` Liming Gao
[not found] ` <15A53EB5F1DA28B3.17041@groups.io>
2019-06-06 4:46 ` 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=4A89E2EF3DFEDB4C8BFDE51014F606A14E46BC99@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