...

      Add VF-C related use case vCPE on daily CI chains 

5. Document current upgrade component strategy(TSC must have) 

6. SECCOM Perform Software Composition Analysis - Vulnerability tables(TSC must have) - plan to solve the most of the security issues, but also depends on the commit resource 

7. SECCOM Password removal from OOM HELM charts(TSC must have) 

8. SECCOM HTTPS communication vs. HTTP(TSC must have) - Based on the resource contribution 

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

Use Case: Residential Broadband vCPE (Approved)

Requirements

Describe the use case this release is targeted for (better if reference to customer requirements).

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

Please update any risk on the centralized wiki page - Frankfurt Risks

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

...