public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	gaoliming <gaoliming@byosoft.com.cn>,
	'Leif Lindholm' <leif@nuviainc.com>,
	"afish@apple.com" <afish@apple.com>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Guptha, Soumya K" <soumya.k.guptha@intel.com>
Cc: "announce@edk2.groups.io" <announce@edk2.groups.io>,
	"'Chang, Abner (HPS SW/FW Technologist)'" <abner.chang@hpe.com>,
	"Zhang, Qi1" <qi1.zhang@intel.com>,
	"marcello.bauer@9elements.com" <marcello.bauer@9elements.com>
Subject: Re: [edk2-devel] Soft Feature Freeze start date delays to 2020-08-24 for edk2-stable202008
Date: Wed, 26 Aug 2020 11:54:24 +0200	[thread overview]
Message-ID: <ea3f01a7-0a62-abb6-f6f4-3b03db971d06@redhat.com> (raw)
In-Reply-To: <CY4PR11MB12884EB6C1429BF576B1A9558C540@CY4PR11MB1288.namprd11.prod.outlook.com>

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):
> <https://edk2.groups.io/g/devel/message/64526>. 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


  reply	other threads:[~2020-08-26  9:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24  1:49 Soft Feature Freeze start date delays to 2020-08-24 for edk2-stable202008 gaoliming
2020-08-24 13:37 ` Laszlo Ersek
2020-08-25  1:19   ` 回复: [edk2-devel] " gaoliming
2020-08-25  2:59     ` Abner Chang
2020-08-26  1:19   ` Yao, Jiewen
2020-08-26  9:54     ` Laszlo Ersek [this message]
2020-08-26 10:16       ` Yao, Jiewen
2020-08-26 12:32         ` 回复: " gaoliming
2020-08-26 14:48         ` Laszlo Ersek
2020-08-26 14:59           ` Yao, Jiewen

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=ea3f01a7-0a62-abb6-f6f4-3b03db971d06@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