To be clear -- the problem *exists* only because the original reporter is stuck behind a restrictive firewall. There is nothing *technically* wrong with the current instructions in

At this point in time we are discussing a workaround for a political problem. But relying on submodules means relinquishing elements of control and consistency (if github goes down, we're

Hey All, I have moved the community meeting to the *2nd* Thursday of July to accommodate the US holiday. The calendar has been

Yes; this is why I suggested dropping "--recursive" from the instructions. As far as I remember, it was meant as a convenience for users cloning the edk2 repo from zero. Can you provide an example

I've updated the calendar entry for the APAC bug triage. I accidentally copy/pasted in the community meeting link when I created the event. The information is now correct. Sorry for anyone who tried

Ray presented how to enhance EFI_MP_SERVICES_PROTOCOL to support V2 extended topology in last week's meeting. Meeting agreed the protocol enhancement proposal (details in slides and summary in

1. BaseTools: Multiple-thread AutoGen Presenter: Bob Feng Slides: https://edk2.groups.io/g/devel/files/Designs/2019/0627/Multiple-thread-AutoGen.pdf * 5 phases: Pre-build, AutoGen, Make, GenFds,

Ray: For FCE & FMMT, I add patch link below. Thanks Liming

[resend from mail client to make sure format is expected.] 1. OOB verification: a common solution providing chain of trust Presenter: Jian Wang Slides:

1. Edk2 Build Cache Enhancement Presenter: Steven Shi Slides: https://edk2.groups.io/g/devel/files/Designs/2019/0726/Edk2BuildCacheEnhancement-v1.pdf * Background (page #2 - #8) Build cache is

The edk2-stable201908 tag is on it's way! Soft feature freeze starts next week. If you have something you're looking to get into this release, now's a great time to email the list with an

Stephano: Is it for bug or features or both? Send RFC to announce@edk2.groups.io or devel@edk2.groups.io or both? Thanks Liming

The soft freeze is for features only. Bug fixes are still allowed. You can read more

Stephano: I have one proposal to add another date for Feature Planning Freeze. This date is ahead of 2 weeks to code Soft Feature Freeze. If the feature is missed in the Feature Planning Freeze

Hi, all Now, we enter into Soft Feature Freeze phase. In this phase, the feature under review will not be allowed to be pushed. The patch review can continue without break in edk2 community. If

I would not object to that. (responding to announce@ as I think that is presently the expected user behavior) Thanks, Laszlo

Yes, I agree as well. Unless anyone objects, I'll add this to the wiki and to our next release planning page. Cheers, Stephano

Hi, all Today, we will enter into Hard Feature Freeze phase until edk2-stable201908 tag is created at 2019-08-30. In this phase, there is no feature to be pushed. The critical bug fix is still

1. Re-architecture of Intel edk2 Redfish POC code on edk2 staging (HPE) Presenter: Chang Abner Slides: https://edk2.groups.io/g/devel/files/Designs/2019/0823 * Background: Redfish project started in

With OSFC being next week, I've canceled the two community meetings. We can handle this one of two ways: If there are a lot of folks at the conference that want to meet in person, we can do that. I'm