From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mx.groups.io with SMTP id smtpd.web11.9094.1598435675655769805 for ; Wed, 26 Aug 2020 02:54:35 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=XQvJXwxm; spf=pass (domain: redhat.com, ip: 216.205.24.124, mailfrom: lersek@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1598435674; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XFD62FTWKmJRKHN+LssMpnWn9ih/9sKSQsJ34NQEjAE=; b=XQvJXwxm5YCFx3dS+/WrfnLr/3cR7bwyf4rSgMStuCJBH07eMwtppIBGtFzhcbOPxYtdmb xe11uC9ebOImLnIzjmX1/RM1n0PTptobv7MwkAqIsHnKQE17N1oxS8/2wF23UtikD3vGzS t/MEzHLEp7FUfGbuST0hthj9tqPjgMs= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-491-PIqpK4UsMpaWrfFu5AA7EA-1; Wed, 26 Aug 2020 05:54:30 -0400 X-MC-Unique: PIqpK4UsMpaWrfFu5AA7EA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A70CF1084C85; Wed, 26 Aug 2020 09:54:28 +0000 (UTC) Received: from lacos-laptop-7.usersys.redhat.com (ovpn-114-182.ams2.redhat.com [10.36.114.182]) by smtp.corp.redhat.com (Postfix) with ESMTP id BEFA660BFA; Wed, 26 Aug 2020 09:54:25 +0000 (UTC) Subject: Re: [edk2-devel] Soft Feature Freeze start date delays to 2020-08-24 for edk2-stable202008 To: "Yao, Jiewen" , "devel@edk2.groups.io" , gaoliming , 'Leif Lindholm' , "afish@apple.com" , "Kinney, Michael D" , "Guptha, Soumya K" Cc: "announce@edk2.groups.io" , "'Chang, Abner (HPS SW/FW Technologist)'" , "Zhang, Qi1" , "marcello.bauer@9elements.com" References: <001501d679b8$bdb3aa20$391afe60$@byosoft.com.cn> <5140ca34-9534-8873-8fbb-e07a9132d53d@redhat.com> From: "Laszlo Ersek" Message-ID: Date: Wed, 26 Aug 2020 11:54:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=lersek@redhat.com X-Mimecast-Spam-Score: 0.002 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Hi Jiewen, On 08/26/20 03:19, Yao, Jiewen wrote: > To clarify below: > I just notice this one week delay. It impacts us. > >> https://edk2.groups.io/g/devel/message/64354 >> [PATCH v4 0/8] Need add a FSP binary measurement > > The SecurityPkg patches have not been approved yet, and Bret and > Jiewen are still testing / discussing (as far as I understand): > . Material for the next > tag. > > [Jiewen] I think the security pkg is already approved by me and Jian > (SecurityPkg maintainer) Bret also provides feedback that it looks > good. The series in question has three SecurityPkg patches: [PATCH v4 1/8] SecurityPkg/TcgEventLogRecordLib: add new lib for firmware measurement [PATCH v4 5/8] SecurityPkg/dsc: add FvEventLogRecordLib [PATCH v4 7/8] SecurityPkg/Tcg2: handle PRE HASH and LOG ONLY As I'm writing this, *none* of the listed patches have any kind of Reviewed-by or Acked-by, either included in the patches themselves, or posted in response to them. > I request to check in to stable202008, if possible. We can do that only if (a) we extend the SFF deadline again, and (b) each of the SecurityPkg patches receives at least an Acked-by from one of the SecurityPkg maintainers, until the new deadline. I'm certainly not against the idea. I don't mind if the release slips some more; it's OK to say that we're not ready to release yet. The point is, as long as we're doing more work for completing the release, we should prolong the stabilization period as well (opportunity for people to test). Thanks, Laszlo