public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] Soft Feature Freeze starts today for edk2-stable201903
Date: Wed, 27 Feb 2019 20:53:49 +0100	[thread overview]
Message-ID: <c17b7918-f65e-aa85-1f41-ed3b45e83670@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E9D43@SHSMSX104.ccr.corp.intel.com>

On 02/27/19 14:16, Gao, Liming wrote:
> Laszlo:
> 
> Thanks
> Liming
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
>> Sent: Tuesday, February 26, 2019 7:55 PM
>> To: Gao, Liming <liming.gao@intel.com>
>> Cc: edk2-devel@lists.01.org
>> Subject: Re: [edk2] [edk2-announce] Soft Feature Freeze starts today for edk2-stable201903
>>
>> On 02/26/19 04:30, Gao, Liming wrote:
>>> Hi, all
>>>   Two features (Add SMM CET support and Add WiFi Connection Manager) get Acked-By or Reviewed-by near the soft feature freeze
>> date. CET is X86 specific feature. WiFi connection manager is the standalone feature. Their impact should be small. So, I suggest to include
>> them in this stable tag edk2-stable201903. If you have different opinion, please raise. If no objection, I will push them late this week.
>>>
>>> Add SMM CET support https://lists.01.org/pipermail/edk2-devel/2019-February/037128.html
>>> NetworkPkg: Add WiFi Connection Manager to NetworkPkg https://lists.01.org/pipermail/edk2-devel/2019-February/037137.html
>>
>> I think the required feedback tags arrived on time, but just barely. (At
>> least in my time zone, CET = UTC+01:00.)
>>
>> - For Jiewen's "[edk2] [PATCH V3 0/4] Add SMM CET support":
>>   - Ray's R-b appeared at 02/22/19 15:29
>>   - My Regression-tested-by appeared at 02/22/19 22:41
>>
>> - For Wang Fan's "[edk2] [Patch V2] NetworkPkg: Add WiFi Connection
>>   Manager to NetworkPkg":
>>   - Jiaxin's R-b appeared at 02/22/19 08:56.
>>
>> I'm OK if both features are pushed.
>>
> Thanks.
> 
>>
>> However, I do have a suggestion for the announcement email, for the
>> future. Given that we've already encountered three cases in this cycle
>> where the feedback tags are on the boundary, I suggest to include an
>> exact timestamp (in the UTC zone) in each announcement. I never expected
>> that this accuracy would be necessary, but apparently it is.
>>
> I suggest to list UTC zone in Proposed Schedule of EDK II Release Planning wiki page as below. I prefer to use PST (UST -8), because edk2-devel Archives (https://lists.01.org/pipermail/edk2-devel/) uses PST time. Then, we can base on the archive mail to check each patch. 
> 
> Date (UTC -8)	Description
> 2019-03-08 Beginning of development
> 2019-02-22 Soft Feature Freeze
> 2019-03-01 Hard Feature Freeze
> 2019-03-08 Release

I think PST (UTC-8) works fine as well, as long as we state it clearly.
Given the time zone, the timestamp is unique, and can be translated to
other time zones.

I do recommend that we specify "midnight" or 00:00:00 as well, however,
if that is our intent. (I'm fine with other hours too, such as "noon"
etc, but it should be specific down to the second. We should be able to
look at any email on the list and determine if it was before or after.
"Equal" should still be accepted.)

Thanks
Laszlo


  reply	other threads:[~2019-02-27 19:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 14:25 [edk2-announce] Soft Feature Freeze starts today for edk2-stable201903 Gao, Liming
2019-02-22 20:19 ` Laszlo Ersek
2019-02-23 14:46   ` Gao, Liming
2019-02-25 11:02     ` Laszlo Ersek
2019-02-26  3:30 ` Gao, Liming
2019-02-26 11:55   ` Laszlo Ersek
2019-02-27 13:16     ` Gao, Liming
2019-02-27 19:53       ` Laszlo Ersek [this message]
2019-02-28  2:22         ` Gao, Liming
2019-02-28 11:57           ` Laszlo Ersek
2019-03-01  1:15             ` Gao, Liming
2019-03-01 14:03               ` Laszlo Ersek

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=c17b7918-f65e-aa85-1f41-ed3b45e83670@redhat.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