From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=209.132.183.28; helo=mx1.redhat.com; envelope-from=lersek@redhat.com; receiver=edk2-devel@lists.01.org Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id D81E8201B0389 for ; Wed, 27 Feb 2019 11:53:51 -0800 (PST) Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 6201E787F1; Wed, 27 Feb 2019 19:53:51 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-125-251.rdu2.redhat.com [10.10.125.251]) by smtp.corp.redhat.com (Postfix) with ESMTP id B02301001947; Wed, 27 Feb 2019 19:53:50 +0000 (UTC) To: "Gao, Liming" Cc: "edk2-devel@lists.01.org" References: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E61EB@SHSMSX104.ccr.corp.intel.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E79EC@SHSMSX104.ccr.corp.intel.com> <357d2043-7645-e63a-fa41-99524c503eab@redhat.com> <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E9D43@SHSMSX104.ccr.corp.intel.com> From: Laszlo Ersek Message-ID: Date: Wed, 27 Feb 2019 20:53:49 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E9D43@SHSMSX104.ccr.corp.intel.com> X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.27]); Wed, 27 Feb 2019 19:53:51 +0000 (UTC) Subject: Re: [edk2-announce] Soft Feature Freeze starts today for edk2-stable201903 X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2019 19:53:52 -0000 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit 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 >> 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