public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Laszlo Ersek <lersek@redhat.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 10:16:32 +0000	[thread overview]
Message-ID: <CY4PR11MB12882580E61BA9D14F281EF08C540@CY4PR11MB1288.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ea3f01a7-0a62-abb6-f6f4-3b03db971d06@redhat.com>

HI Laszlo
I checked the history.

Jiewen replied " [PATCH v3 0/8] Need add a FSP binary measurement" with review-by on V3 patch series in August 15, with comment to rename FvEventLogRecordLib to TcgEventLogRecordLib.
Qi sent v4 series in August 17, with only naming change from FvEventLogRecordLib to TcgEventLogRecordLib.
Jian replied "[PATCH v3 0/8] Need add a FSP binary measurement" with reviewed-by on V3 patch series in August 18.

So I treat this patch series is qualified to check in (since V4 adopted my comment). But please let me know if there is any misunderstanding.


When I am about to merge, I am told that we are in SFF and I cannot check in.
According to the plan, I will check in after August 28, which is end of August. It is still OK for me.
2020-08-14  Soft Feature Freeze
2020-08-21  Hard Feature Freeze
2020-08-28  Release

But now, if we need delay one week, then the final release data will be September. If I cannot check in now, I will have to check in at September.
That is why I said, it impacts me, because of this one week delay.

Thank you
Yao Jiewen


> -----Original Message-----
> From: Laszlo Ersek <lersek@redhat.com>
> Sent: Wednesday, August 26, 2020 5:54 PM
> To: Yao, Jiewen <jiewen.yao@intel.com>; devel@edk2.groups.io; gaoliming
> <gaoliming@byosoft.com.cn>; 'Leif Lindholm' <leif@nuviainc.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; 'Chang, Abner (HPS SW/FW Technologist)'
> <abner.chang@hpe.com>; Zhang, Qi1 <qi1.zhang@intel.com>;
> marcello.bauer@9elements.com
> Subject: Re: [edk2-devel] Soft Feature Freeze start date delays to 2020-08-24 for
> edk2-stable202008
> 
> 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 10:16 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
2020-08-26 10:16       ` Yao, Jiewen [this message]
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=CY4PR11MB12882580E61BA9D14F281EF08C540@CY4PR11MB1288.namprd11.prod.outlook.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