Date   

EDK II Stable Tag release edk2-stable202111 completed and Hard Freeze extend to 2021-12-03

gaoliming
 

Hi, all



The tag edk2-stable202111 has been created.
https://github.com/tianocore/edk2/releases/tag/edk2-stable202111

git clone -b edk2-stable202111 https://github.com/tianocore/edk2.git



The tag edk2-stable202111 has been added into the main EDK II Wiki page.

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II



Next edk2 stable tag (edk2-stable202202) planning has been added into wiki
page.

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g.



If you have ideas for features in the next stable tag, please enter a
Bugzilla for evaluation. Please let me know if there are existing open
Bugzilla entries that should be targeted at this next stable tag.



But now, we are still in hard freeze period until Uncrustify patches are
merged. The plan is to extend one week hard freeze to 2021-12-03. Thank you
for your cooperation and patience.



Thanks

Liming


Call for Topics - Community Meeting Dec 2

Teng, Lynn L
 

Hello All,

Please let me know by November 26th if you have any topics you would like to include in the agenda for the December 2nd Community Meeting.

Thank you,
Lynn Teng


Inclusive Language Update RFC

Teng, Lynn L
 

Hello all,

We have updated the Overview section of the Inclusive Language Guidelines to clarify two things.
1. Which version (via date) of the [[UEFI Inclusive Language Implementation Guidelines|https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf]] we will be following so we do not have a moving target.
2. Defining "_non-legacy_" and "_legacy_".

***

## Overview

To promote a more inclusive and open ecosystem, TianoCore is dedicated to removing archaic terminology that holds negative connotation.
In collaboration with UEFI, we will be following the same [[Inclusive Language Implementation Guidelines|https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf]] (as of Nov 1, 2021) as stated on [[UEFI.org|https://uefi.org/]].

In our plan below, we have steps for dealing with both "_non-legacy_" and "_legacy_". For these terms we define "_non-legacy_" as UEFI BIOS/specifications and beyond, where as "_legacy_" is BIOS/specifications that predates UEFI. There are references to legacy specifications not controlled by the TianoCore Community, and they may not follow these guidelines. In order to preserve compatibility for code that reads on legacy specifications, particularly where that specification is no longer under maintenance or development, language in this specification may appear out of sync with the guidelines. In these cases, the Community will work with other standards development bodies to eliminate such examples over time. In the meanwhile, by acknowledging and calling attention to this issue the hope is to promote discussion and action towards more complete use of Inclusive Language reflective of the diverse and innovative population of the technical community that works on standards.


## Plan

1. Announcement of intent, and all check-ins from here onwards will need to abide by Inclusive Language Implementation Guidelines
2. Scrubbing of all comments, documentation, and Wiki pages
3. Scrubbing of all non-legacy code
4. Working with UEFI to scrub legacy code


## Implementation Guidelines

### Master/Slave to not be used together nor alone.
Alternatives:
Master | Slave
-------|-------
Main | Secondary, Subordinate
Primary | Secondary, Replica
Host | Target
Leader | Follower
Orchestrator | Worker
Initiator | Responder

Or similar descriptive terminology

### Blacklist/Whitelist to not be used together nor alone.
Alternatives:
Blacklist | Whitelist
----------|----------
Blocklist | Passlist
Denylist | Allowlist
Refused, Denied | Permitted

Or similar descriptive terminology

***

Please provide any input you may have with regards to these changes by Nov 26th.

Thank you,
Lynn Teng


Hard Feature Freeze starts now for edk2-stable202111

gaoliming
 

Hi, all

Today, we enter into Hard Feature Freeze phase until edk2-stable202111 tag
is created at 2021-11-26. Tag edk2-stable202111-rc1
(466ebdd2e0919c1538d03cd59833704bd5e1c028) has been created for evaluation.
In this phase, there is no feature to be pushed. The critical bug fix is
still allowed.



If the patch is sent after Hard Feature Freeze, and plans to catch this
stable tag, please add edk2-stable202111 key words in the patch title and
BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.



Below is edk2-stable202111 tag planning.

Date (00:00:00 UTC-8) Description

2021-08-30 Beginning of development

2021-11-08 Soft Feature Freeze

2021-11-12 Hard Feature Freeze

2021-11-26 Release



Thanks

Liming


Re: TianoCore Community Meeting Minutes - November 2021

Rebecca Cran
 

On 11/9/21 3:03 PM, Teng, Lynn L wrote:

- **Question from Community**: Should we formalize the "Get Started with Git" and clean it up/raise awareness?

To clarify, the page is https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers - i.e. "Laszlo's unkempt git guide for edk2 contributors and maintainers" that I suggested renaming to something more like "Getting started with Git" or "Setting or your TianoCore development environment".


--
Rebecca Cran


TianoCore Community Meeting Minutes - November 2021

Teng, Lynn L
 

# TianoCore Community Meeting
November 4, 2021

**Highlights:**
* **Python 3 is here and the removal of Python 2 is coming soon**
* **Our Inclusive Language commitment and activities will begin soon**
* **Request to the Community**: Please review the list of features on [Bugzilla](https://bugzilla.tianocore.org/show_bug.cgi?id=3446) to have them ready for 2.8
* **Request to the Community**: When can we delete the Python BaseTool source from the EDK II repo and move towards using the Python BaseTools PIP Install?
* **Request to the Community**: Help identify the status of each EDK II Platform and who are the maintainers?
* **Request to the Community**: Evaluate the source format being produced by Uncrustify and how it works. If you have any questions or issues with either, please let us know by the beginning of December.


# Meeting Minutes:

1) **Event Updates (_5 minutes_)**
- No Updates

2) [**Stable Tag Updates (_5 minutes_)**](https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning)
- 2021-11-08 Soft Feature Freeze
- 2021-11-12 Hard Feature Freeze
- 2021-11-26 Release

3) **Stewards Download (_20 minutes_)**
- UEFI 2.8 report
- **Request to the Community**: Please review the list of features on Bugzilla to have them ready for 2.8
- Targeting first release in 2022 to have all UEFI 2.8 features done ([Bugzilla 3446](https://bugzilla.tianocore.org/show_bug.cgi?id=3446))
- Python for BaseTools are ready for PIP install
- Our goal is to move everyone to pip installing rather than maintaining a duplicate copy of the sources/repos
- We would like to delete the Python BaseTools source from the EDK II repo
- **Question from Community**: Would it be possible to full BaseTools from a submodule?
- **Request to the Community**: When can we delete the Python BaseTool source from the EDK II repo and move towards using the Python BaseTools PIP Install?
- EDK II Platforms Repository
- We have stable tags for EDK II, but not EDK II Platforms
- Each platform is at a different level of maintenance
- Only keep maintained platforms in master (to be renamed to main)
- Having a separate branch for unmaintained stable branches, _different from under development branches_
- Establish stable tag for EDK II Platforms
- **Request to the Community**: Help identify the status of each EDK II Platform and who are the maintainers?
- Bring the platforms up to being compatible with latest the EDK II.
- Would like to have a stable tag and CI to the Platforms to improve maintainability.
- **Question from Community**: What to do about platforms that haven't been touched in years, but developers would like to use?
- **Discussion**: Having an inventory of physical platforms owned by individual platform owners
- Would be good to document a process for adding physical platforms for the community to access
- Standardize API for connecting and getting simple status from those physical platforms
- Uncrustify (_a code clean up tool_)
- A version is being created to clean EDK II code
- We would like to ensure that any clean up of the EDK II source does not affect its functionality
- Our target to begin cleaning is after the next stable tag release
- **Request to the Community**: Evaluate the source format being produced by Uncrustify and how it works. If you have any questions or issues with either, please let us know by the beginning of December.

4) **Opens (_30 minutes_)**
- **Python 3 is here and the removal of Python 2 is coming soon**
- Our Inclusive Language commitment and activities will begin soon
- Master will be renamed to Main in git
- First we need to do the full evaluation of how changing the name will affect the repositories
- We will proceed with repository renaming in a layered approach
1. All new repositories must be named Main
2. Convert repositories that don't have active CI
3. Convert the rest of the repositories when possible
- All developers will be informed when a repo is going being changed and how to handle the change
- All other Inclusive Language commits will begin as community code reviews for catching banned words
- We will build a wiki page with a task list of work to be done
- **Question from Community**: Should we formalize the "Get Started with Git" and clean it up/raise awareness?
- **Answer**: The community has write permissions to update any wiki pages, so we can work together to update and maintain it
- **Question from Community**: Is there an update on the pull request feature for switching email based patches to pull requests?
- **Answer**: We do not have update on that currently, but it's on the to do list


Re: Inclusive Language RFC

Teng, Lynn L
 

Hello Sean,

You make a good point.

I will remove both steps 3.1 and 4.1 from the plan for now so we can focus on the main proposal.
We can open a discussion later on to determine how best to maintain inclusive language once the codebase has been updated.

Here is the updated proposal:

***

## Overview

To promote a more inclusive and open ecosystem, TianoCore is dedicated to removing archaic terminology that holds negative connotation.
In collaboration with UEFI, we will be following the same [Inclusive Language Implementation Guidelines](https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf) as stated on UEFI.org](https://uefi.org/).


## Plan

1. Announcement of intent, and all check-ins from here onwards will need to abide by Inclusive Language Implementation Guidelines
2. Scrubbing of all comments, documentation, and Wiki pages
3. Scrubbing of all non-legacy code
4. Working with UEFI to scrub legacy code


## Implementation Guidelines

### Master/Slave to not be used together nor alone.
Alternatives:
Master | Slave
-------|-------
Main | Secondary, Subordinate
Primary | Secondary, Replica
Host | Target
Leader | Follower
Orchestrator | Worker
Initiator | Responder

Or similar descriptive terminology

### Blacklist/Whitelist to not be used together nor alone.
Alternatives:
Blacklist | Whitelist
----------|----------
Blocklist | Passlist
Denylist | Allowlist
Refused, Denied | Permitted

Or similar descriptive terminology

-----Original Message-----
From: announce@edk2.groups.io <announce@edk2.groups.io> On Behalf Of Sean
Sent: Monday, November 1, 2021 1:16 PM
To: Teng, Lynn L <lynn.l.teng@intel.com>; announce@edk2.groups.io
Subject: Re: [edk2-announce] Inclusive Language RFC

Content looks great except "Plan 4.1."
I don't see a commit hook as a solution that works for this community.
I would think the plan would leverage pr-gate/ci to enforce this?
Otherwise, it is yet another rule and place to cause code-review and contribution friction.

Thanks
Sean




On 10/25/2021 11:57 AM, Teng, Lynn L wrote:
Hello all,

Please provide your feedback and comments to the Inclusive Language Plan below over the next two weeks (10/25-11/05). Thank you in advance for your contributions.


***

## Overview

To promote a more inclusive and open ecosystem, TianoCore is dedicated to removing archaic terminology that holds negative connotation.
In collaboration with UEFI, we will be following the same [Inclusive Language Implementation Guidelines](https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf) as stated on [UEFI.org](https://uefi.org/).


## Plan

1. Announcement of intent, and all check-ins from here onwards will
need to abide by Inclusive Language Implementation Guidelines 2.
Scrubbing of all comments, documentation, and Wiki pages 3. Scrubbing
all non-legacy code 3.1. Integrate open-source commit hook that will
warn submitter of violations 4. Working with UEFI to scrub legacy code
4.1. Update commit hook to block submissions with violations


## Implementation Guidelines

### Master/Slave to not be used together nor alone.
Alternatives:
Master | Slave
-------|-------
Main | Secondary, Subordinate
Primary | Secondary, Replica
Host | Target
Leader | Follower
Orchestrator | Worker
Initiator | Responder

Or similar descriptive terminology

### Blacklist/Whitelist to not be used together nor alone.
Alternatives:
Blacklist | Whitelist
----------|----------
Blocklist | Passlist
Denylist | Allowlist
Refused, Denied | Permitted

Or similar descriptive terminology





TianoCore Community Meeting Agenda - November

Teng, Lynn L
 

Hello All,

Our agenda for this month's meeting will be as follows:

1) Event Updates (_5 minutes_)
2) Stable Tag Updates (_5 minutes_)
3) Stewards Download (_20 minutes_)
4) Opens (_30 minutes_)
4.1) Inclusive Language
4.2) Python 3

Best regards,
Lynn Teng


Re: Inclusive Language RFC

Sean
 

Content looks great except "Plan 4.1."
I don't see a commit hook as a solution that works for this community. I would think the plan would leverage pr-gate/ci to enforce this? Otherwise, it is yet another rule and place to cause code-review and contribution friction.

Thanks
Sean

On 10/25/2021 11:57 AM, Teng, Lynn L wrote:
Hello all,
Please provide your feedback and comments to the Inclusive Language Plan below over the next two weeks (10/25-11/05). Thank you in advance for your contributions.
***
## Overview
To promote a more inclusive and open ecosystem, TianoCore is dedicated to removing archaic terminology that holds negative connotation.
In collaboration with UEFI, we will be following the same [Inclusive Language Implementation Guidelines](https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf) as stated on [UEFI.org](https://uefi.org/).
## Plan
1. Announcement of intent, and all check-ins from here onwards will need to abide by Inclusive Language Implementation Guidelines
2. Scrubbing of all comments, documentation, and Wiki pages
3. Scrubbing all non-legacy code
3.1. Integrate open-source commit hook that will warn submitter of violations
4. Working with UEFI to scrub legacy code
4.1. Update commit hook to block submissions with violations
## Implementation Guidelines
### Master/Slave to not be used together nor alone.
Alternatives:
Master | Slave
-------|-------
Main | Secondary, Subordinate
Primary | Secondary, Replica
Host | Target
Leader | Follower
Orchestrator | Worker
Initiator | Responder
Or similar descriptive terminology
### Blacklist/Whitelist to not be used together nor alone.
Alternatives:
Blacklist | Whitelist
----------|----------
Blocklist | Passlist
Denylist | Allowlist
Refused, Denied | Permitted
Or similar descriptive terminology


Inclusive Language RFC

Teng, Lynn L
 

Hello all,

Please provide your feedback and comments to the Inclusive Language Plan below over the next two weeks (10/25-11/05). Thank you in advance for your contributions.


***

## Overview

To promote a more inclusive and open ecosystem, TianoCore is dedicated to removing archaic terminology that holds negative connotation.
In collaboration with UEFI, we will be following the same [Inclusive Language Implementation Guidelines](https://uefi.org/sites/default/files/resources/UEFI_Inclusive%20Language.pdf) as stated on [UEFI.org](https://uefi.org/).


## Plan

1. Announcement of intent, and all check-ins from here onwards will need to abide by Inclusive Language Implementation Guidelines
2. Scrubbing of all comments, documentation, and Wiki pages
3. Scrubbing all non-legacy code
3.1. Integrate open-source commit hook that will warn submitter of violations
4. Working with UEFI to scrub legacy code
4.1. Update commit hook to block submissions with violations


## Implementation Guidelines

### Master/Slave to not be used together nor alone.
Alternatives:
Master | Slave
-------|-------
Main | Secondary, Subordinate
Primary | Secondary, Replica
Host | Target
Leader | Follower
Orchestrator | Worker
Initiator | Responder

Or similar descriptive terminology

### Blacklist/Whitelist to not be used together nor alone.
Alternatives:
Blacklist | Whitelist
----------|----------
Blocklist | Passlist
Denylist | Allowlist
Refused, Denied | Permitted

Or similar descriptive terminology


Call for Topics - Community Meeting Nov 4

Teng, Lynn L
 

Hello All,

Please let me know by October 29th if you have any topics you would like to include in the agenda for the November 4th Community Meeting.

Thank you,
Lynn Teng


TianoCore Community Meeting Minutes - October 2021

Soumya Guptha
 

TianoCore Community Meeting

October 7, 2021



Events

UEFI Plugfest:

No new updates since last month.

Past AR review from September -

o Community Action: provide input to Dick Wilkins Dick_Wilkins@phoenix.com<mailto:Dick_Wilkins@phoenix.com<mailto:Dick_Wilkins@phoenix.com%3cmailto:Dick_Wilkins@phoenix.com>> on these questions -

* Is your company interested in sponsoring?

* Are you willing to pay for the conference?



Community Response - Community thinks that it's useful to have a face to face event.

Paying for the conference maybe fine for those that need to pay for hotel and flight.

Aligning with UEFI plugfest is beneficial for the TianoCore design/technical roadmap discussions and for the TianoCore community to come together.





Stable Tag updates:

Stable tag 202111 is collecting features.

Soft freeze on Nov 8th.

Community Action: please send your feature requests ahead of time to Liming.





Stewards Download:

1. Inclusive language: Stewards discussed TianoCore to follow inclusive language and layout the guidelines. Community manager will drive further conversations with stewards and community in the upcoming weeks.
2. Discussion around Uncrustify tool.

Reduces code review time and provides consistent code base when having to recode so you don't see mixed styles in diff parts of the tree.

Community action - review the code style and provide feedback if you like it or not and what changes would you like to see.

EDK2 C coding style is not identical to Uncrustify. Should we change EDK2 style?

Please follow the discussion here - https://edk2.groups.io/g/devel/topic/progress_on_getting/84932137?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,84932137,previd=1633659901428425771,nextid=1633620778663080075&previd=1633659901428425771&nextid=1633620778663080075

1. Felix had sent RFC on static analysis on EDK2 but no feedback from the community. Community to send feedback to Felix.

Please follow the discussion here - https://edk2.groups.io/g/rfc/topic/rfc_static_analysis_in_edk2/85318202?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,85318202,previd=1633604560724866953,nextid=1619704994055247213&previd=1633604560724866953&nextid=1619704994055247213

1. Spam on Bugzilla (Mike Kinney) - we need to change the configuration of TianoCore Bugzilla. We have been handling so far by disabling those spammers and these emails remain in our mailing list.

a. Mike has handled it by changing the permissions disabling for people to create accounts to avoid the spam.

Open: What process should we follow?

AR: Mike and Liming will follow up in the email on the TianoCore Bugzilla account creation process and post it. wiki pages need to be updated as well.



Opens:

1. Update from Soumya Guptha: Lynn Teng from Intel will be acting as Community manager and picking up community management responsibilities starting this month. Please extend your support to Lynn Teng. Soumya Guptha will be stepping away from the Community management during this time.
2. Update from Nate Desimone -Intel(r) Xeon Scalable Processors, Ice Lake and Cooper Lake min platform has been released.
3. OCP Global Summit: Scheduled on Nov 9-10, 2021. This year is a hybrid model - both in-person and online, held in San Jose, California, US.

OCP summit schedule here - https://2021ocpglobal.fnvirtual.app/a/schedule

Check out these sessions -

1) Wed, November 10, 2:15pm - 2:30pm | SJCC - Concourse Level - 210BF FSP and MinPlatform for Sapphire Rapids Intel(r) Xeon(r) Scalable Processors by Nate Desimone and Isaac Oram (Intel).

2) Wed, November 10, 4:15pm - 4:30pm | SJCC - Concourse Level - 210BF Enabling Runtime RAS on Xeon OCP Platforms Using Intel FSP and Coreboot by Ruth Li





Regards,

Soumya Guptha

TianoCore Community Manager


Intel® FSP External Architecture Specification v2.3 Has Been Released

Nate DeSimone
 

Hi Everyone,

We are pleased to announce that the FSP External Architecture Specification v2.3 has been posted to https://www.intel.com/fsp!

Highlights

* FSP_NON_VOLATILE_STORAGE_HOB2 – A new architectural HOB has been added for storage of MRC training data. While this HOB serves the same purpose as the original FSP_NON_VOLATILE_STORAGE_HOB, it allows >64KB of MRC training data to be stored. Some of Intel’s upcoming designs will require the storage of >64KB of MRC training data, so this addition is being made in advance. Bootloaders should practice defensive programming and first search for FSP_NON_VOLATILE_STORAGE_HOB2, and only search for FSP_NON_VOLATILE_STORAGE_HOB if the former is not found in the HOB list. This algorithm will guarantee compatibility with all FSP 2.x specification versions.

* FSP Version Numbers – A new ExtendedImageRevision field has been added to the FSP_INFO_HEADER. This expands the size of the Revision and Build Number fields of the FSP version number from 8 bits to 16 bits. This is done by adding a high-order byte to each of those fields. If the ExtendedImageRevision field is present, then the FSP version number is decoded as follows:

Build Number = (ExtendedImageRevision[7:0] << 8) | ImageRevision[7:0]
Revision = (ExtendedImageRevision[15:8] << 8) | ImageRevision[15:8]
Minor Version = ImageRevision[23:16]
Major Version = ImageRevision[31:24]

Roadmap

Both Meteor Lake and Sapphire Rapids will require storage of >64KB of MRC training data. Therefore, we recommend that bootloaders plan to have support for FSP 2.3 ready by early next year.

Does Anything Need to Change in EDK II?

Both IntelFsp2Pkg and IntelFsp2WrapperPkg will need to be modified to define and implement the FSP_NON_VOLATILE_STORAGE_HOB2 and ExtendedImageRevision. Additionally, MinPlatformPkg/FspWrapper will need modifications to implement FSP_NON_VOLATILE_STORAGE_HOB2. The community can expect patches from Intel to implement these changes.


TianoCore Community Meeting Minutes - September 2021

Soumya Guptha
 

TianoCore Community Meeting
September 2, 2021

Events:
Google Summer of Code:
* A very successful summer with students completing the projects and code checked in to EDK2 repo.
* Those projects that need to be added to the EDK2 master, mentors need to bring those to Liming and Maintainers attention. Maintainers of those projects to discuss with Liming and add those projects that are candidates for the EDK2 master, to the upcoming stable tag releases.
* Community Action:
o Mentors to communicate to Liming if any of the projects are a candidate to EDK2 master.
o Need to advertise successes with an email of the summary/projects, share the content. Soumya to discuss with Nate.

UEFI Plugfest update from Dick Wilkins:
* Concerns around pandemic travel that may impact April '22 plugfest. Will people be able to travel? Still evaluating.
* Budget concerns: UEFI forum is trying to keep the dues low. Sponsorships from many companies are impacted which impacts the budget for plugfest. Questions are being raised - do we have enough new technologies to provide test material for people to get together for testing, should we have a plugfest? Can we find the funds to run the plugfest?
* Can we charge registration fees for the attendees? to cover food, evening event etc. like any other industry events.
o Community Action: provide input to Dick Wilkins Dick_Wilkins@phoenix.com<mailto:Dick_Wilkins@phoenix.com> on these questions -
* Is your company interested in sponsoring?
* Are you willing to pay for the conference?

Stable Tag updates:
* Stable tag 202108 has been released.
* Next stable tag 202111 is collecting features.
* Community Action: please send your feature requests ahead of time to Liming.

Stewards Download:
* Not much update for this month.
* Stable tag 202108 release went smooth. The new process with 2 week gap between hard freeze and release worked well.

Opens: none



--------------


Regards,
Soumya Guptha

TianoCore Community Manager


EDK II Stable Tag release edk2-stable202108 completed

gaoliming
 

Hi, all



The tag edk2-stable202108 has been created.
https://github.com/tianocore/edk2/releases/tag/edk2-stable202108

git clone -b edk2-stable202108 https://github.com/tianocore/edk2.git



The tag edk2-stable202108 has been added into the main EDK II Wiki page.

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II



The quiet period has now ended. Thank you for your cooperation and patience.
Normal commits can now be resumed.



Next edk2 stable tag (edk2-stable202111) planning has been added into wiki
page.

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g.



If you have ideas for features in the next stable tag, please enter a
Bugzilla for evaluation. Please let me know if there are existing open
Bugzilla entries that should be targeted at this next stable tag.



Thanks

Liming


TianoCore Meeting Minutes - August 2021

Soumya Guptha
 

TianoCore Community Meeting

August 12, 2021



EVENTS:

Google Summer of Code:

* 7 projects were selected, one of the projects got dropped before mid-term. All projects are listed here: https://summerofcode.withgoogle.com/organizations/6376892141142016/
* All 6 are doing well. Code review in progress. Projects are targeted to be complete by Aug 23.
* Students should have the patches submitted by Aug 16, so we can get them reviewed and merge by Aug 23.
* Community Action: provide feedback to students. Next week, we need maintainers to review patches.

No new updates on UEFI plugfest



Stable Tag updates:

* EDK2 Stable Tag 202108 soft freeze complete, hard freeze (8/13).
* Details here: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning
* We are maintaining 2 weeks between hard freeze and final Release. Previously we had 1 wk gap between hard freeze and release. Now with a 2 week gap allows us to find issues and fix those before releasing. Moving forward we will maintain 2 week gap between hard freeze and Release.
* Stable tag improvements: Liming will start adding tags for soft and hard freeze. This will help the community as they pull in the tags, when issues are reported, test issues/results can be tagged to the soft/hard freeze. This is change from what we had earlier.



Community Opens:

1. Open from Rebecca - EDK2 Lib C patch. Lib C has not updated for a while. Unknown state on support and maintainership.

* Update from Mike Kinney: There are no maintainers currently. Its based on a very old version of the code, need to bring it up to date. There are a few proposals in progress. There is active discussion in the email distribution list (dev list). Does community have any concerns around current proposals? (staging repository CDE package, Standard lib package (PDC lib) in staging).
* Community Action: We would like community involved in this discussion. If there are any concerns around downstream use around the licenses, please let us know.
Do we want to add full standard C lib support to EDK2 repo? We need drive consensus within the next 2-4 weeks.

1. Open from Rebecca: Xcode Wiki page needs to be updated. It seems to be slow. Andrew has looked into it.

* Action: Rebecca send an email on the mailing list. Status: Closed. Liming has updated.

1. Open from Felix on Coverity & Static analyzer for EDK2 -

* Mike Kinney noted: It's not maintained currently. Goal is to have the CI process set up by this year.

Review the content with TianoCore Infosec community.

* Mike Kinney noted potential approaches: To eliminate false positives or mark as not an issue if its a false positive so we are aware. Open Coverity is a powerful tool for open source projects. it's a gap currently in EDK2 project to not have a static analysis tool. We need resources to work on the CI system.
* Felix is looking at Coverity and interested in supporting.
* Action: Felix to open a RFC discussion and lead a planning discussion. We don't do static analysis today as part of the open source project.


Regards,
Soumya Guptha

TianoCore Community Manager


Hard Feature Freeze starts now for edk2-stable202108

gaoliming
 

Hi, all

Today, we enter into Hard Feature Freeze phase until edk2-stable202108 tag
is created at 2021-08-27. Tag edk2-stable202108-rc1
(6fdd1c13a734609aff68d37e606e995d673d9aeb) has been created for evaluation.
In this phase, there is no feature to be pushed. The critical bug fix is
still allowed.



If the patch is sent after Hard Feature Freeze, and plans to catch this
stable tag, please add edk2-stable202108 key words in the patch title and
BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.



Below is edk2-stable202108 tag planning.

Date (00:00:00 UTC-8) Description

2021-05-28 Beginning of development

2021-08-09 Soft Feature Freeze

2021-08-13 Hard Feature Freeze

2021-08-27 Release



Thanks

Liming


Soft Feature Freeze starts NOW for edk2-stable202108

gaoliming
 

Hi, all

We enter into Soft Feature Freeze phase for edk2-stable202108. The tag
edk2-stable202108-rc0 (d02dbb53cd78de799e6afaa237e98771fb5148db) has been
created.



In this phase, the feature under review will not be allowed to be pushed.
The feature passed review can still be merged. The patch review can continue
without break in edk2 community. If the patch is sent before Soft Feature
Freeze, and plans to catch this stable tag, the patch contributor need reply
to his patch and notify edk2 community. If the patch is sent after Soft
Feature Freeze, and plans to catch this stable tag, please add
edk2-stable202108 key words in the patch title and BZ, so the community know
this patch target and give the feedback.



Below is Proposed Schedule for edk2-stable202108 tag
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g

Date (00:00:00 UTC-8) Description

2021-05-28 Beginning of development

2021-08-09 Soft Feature Freeze

2021-08-13 Hard Feature Freeze

2021-08-27 Release



Thanks

Liming


Update stable tag release date for future stable tag

gaoliming
 

Hi, all

edk2 stable tag 202108 release date is updated as below. And, rc0 tag is
created for SFF, rc1 tag is created for HFF. If the feature is for 202108
stable tag, please make sure its patches pass code review before SFF date
2021-08-09.



Date (00:00:00 UTC-8) Description for stable tag 202108

2021-05-28 Beginning of development

2021-08-09 Soft Feature Freeze (tag edk2-stable202108-rc0)

2021-08-13 Hard Feature Freeze (tag edk2-stable202108-rc1)

2021-08-27 Release



Stable tag planning
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Plannin
g is also updated.



Thanks

Liming

发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 gaoliming
发送时间: 2021年7月5日 9:09
收件人: devel@edk2.groups.io
抄送: leif@nuviainc.com; afish@apple.com; 'Kinney, Michael D'
<michael.d.kinney@intel.com>; lersek@redhat.com; 'Guptha, Soumya K' <soumya.
k.guptha@intel.com>
主题: [edk2-devel] Update stable tag release date for future stable tag



Hi, all

Based on the proposal in <https://edk2.groups.io/g/rfc/message/684>
https://edk2.groups.io/g/rfc/message/684, Soft Feature Freeze phase (SFF)
will be shorten to 5 days for the reviewed patch merge, Hard Feature Freeze
phase (HFF) will be extended to 2 weeks for downstream verification.
Meanwhile, tag edk2-stableYYYYMM-rc0 will be created for SFF, and
edk2-stableYYYYMM-rc1 will be created for HFF. The detail proposal can refer
to <https://edk2.groups.io/g/rfc/message/684>
https://edk2.groups.io/g/rfc/message/684. For next stable tag 202108, the
proposed new date will be the below one. If you have any comments, please
reply this mail before July 12th.



Date (00:00:00 UTC-8) Description for stable tag 202108

2021-05-28 Beginning of development

2021-08-09 Soft Feature Freeze

2021-08-13 Hard Feature Freeze

2021-08-27 Release



Thanks

Liming


TianoCore Community Meeting Minutes - July

Soumya Guptha
 

TianoCore Community Meeting



July 8, 2021



EVENTS:

Google Summer of Code:

* TianoCore projects are listed here: https://summerofcode.withgoogle.com/organizations/6376892141142016/
* Going well. Midterm reviews are due in a few days.
* Students have started submitting patches. Students need to complete projects by mid-august.
* Community Action: If you see any emails from the students, please provide feedback and support them.



Stable Tag updates:

EDK2 Stable Tag 202108 is collecting features. Please send in if you have any feature requests.

* Details here: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning


Stewards Meeting Download (update from Mike Kinney)

* No download this month.

Opens

* Philippe Mathieu-Daudé (Red Hat) plans to cover OVMF activities, collaborating with Lazlo (Red Hat).
* Mike Kinney updated on - Enabling pull request. Mergify feature is now much simpler and a big improvement on configuration file, maintainers workflow. Maintainers don't have to manually rebase pull request when change requests occur. This feature will be included as part of the upcoming stable tag.



Regards,

Soumya Guptha

TianoCore Community Manager

1 - 20 of 269