From: "Liming Gao" <liming.gao@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
"Laszlo Ersek <lersek@redhat.com> (lersek@redhat.com)"
<lersek@redhat.com>,
"Andrew Fish (afish@apple.com)" <afish@apple.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: edk2-stable201905 features and soft/hard freeze and release date
Date: Fri, 24 May 2019 08:00:15 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E450C36@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B9D1BFDD@ORSMSX113.amr.corp.intel.com>
Mike:
>-----Original Message-----
>From: Kinney, Michael D
>Sent: Friday, May 24, 2019 2:16 AM
>To: Leif Lindholm <leif.lindholm@linaro.org>; Gao, Liming
><liming.gao@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>
>Cc: devel@edk2.groups.io; Wang, Jian J <jian.j.wang@intel.com>;
>ard.biesheuvel@linaro.org; Laszlo Ersek <lersek@redhat.com>
>(lersek@redhat.com) <lersek@redhat.com>; Andrew Fish (afish@apple.com)
><afish@apple.com>; Cetola, Stephano <stephano.cetola@intel.com>
>Subject: RE: edk2-stable201905 features and soft/hard freeze and release
>date
>
>> -----Original Message-----
>> From: Leif Lindholm [mailto:leif.lindholm@linaro.org]
>> Sent: Thursday, May 23, 2019 10:17 AM
>> To: Gao, Liming <liming.gao@intel.com>
>> Cc: devel@edk2.groups.io; Kinney, Michael D
>> <michael.d.kinney@intel.com>; Wang, Jian J
>> <jian.j.wang@intel.com>; ard.biesheuvel@linaro.org;
>> Laszlo Ersek <lersek@redhat.com> (lersek@redhat.com)
>> <lersek@redhat.com>; Andrew Fish (afish@apple.com)
>> <afish@apple.com>; Cetola, Stephano
>> <stephano.cetola@intel.com>
>> Subject: Re: edk2-stable201905 features and soft/hard
>> freeze and release date
>>
>> On Thu, May 23, 2019 at 07:46:37AM +0000, Gao, Liming
>> wrote:
>> > >* 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.
>>
>> I don't really want to get into bikeshedding here, but
>> I just want to
>> point out that we do not need to rename the stable tag
>> just because of
>> the release being pushed out.
>>
>> For my Linaro firmware releases, I tend to stick with
>> the original
>> name regardless. I recently published 19.03 :)
>>
>
>I agree. We should not change the release name. The goal
>is to finish the work as fast as possible. If we are
>successful, the delay could be limited to a few days.
>
I understand. So, we still keep stable201905.
Now, I don't get the message from Wang, Jian and Ard.
So, I don't know how much effort are required. Because
I have sent the announce to enter in the soft freeze, I think
we are still in the soft freeze. I will delay hard freeze announcement
until we have the answer.
>> Best Regards,
>>
>> Leif
next prev parent reply other threads:[~2019-05-24 8:00 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
2019-05-23 17:16 ` Leif Lindholm
2019-05-23 18:15 ` Michael D Kinney
2019-05-24 8:00 ` Liming Gao [this message]
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E450C36@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