Page History

Release 7 target date is Dec 15th 2022.

Blue Prints Participating in Release 7

Internal Target date to meet Rel 7 Criteria is TBD

(To be updated)

No.

Project Name

TSC Subgroup Release Status

Is this your first release

Blue Print Stage

Self-Certify
Incubation
Mature
Core

CD Logs URL to be used for review

(Column filled in by PTLs)

How to: Push Logs to Nexus

Jenkins Master for Private Lab

Jenkins Peering Guide

Example:

KubeEdge BP Test Documents

Link to executive one pager

(editable doc format)

(Column filled in by PTLs)

API Info Reporting Review

(Column filled in by API Subcommittee)

(note for PTLs – go here for steps to fill in project API info form)

BluVal

BlueVal Logs or Manual Logs

Bluval User Guide

Security

Certification

(TO be filled by Security Subcommittee)

Pass/Fail Criteria: Steps To Implement Security Scan Requirements

Exception requests should be filed at:

Release 6: Akraino CVE and KHV Vulnerability Exception Request

Upstream Review (Column filled by Upstream Subcommitte)

( PTL can go to R7 Release Upstream Compliance )

Date ready for TSC review

(Column filled in by PTLs)

TSC Review Date

(Column filled in by TSC)

//The following needs to be updated accordingly.

For details, refer to the following requirements:

Classes of release 7 Blueprints and the requirements to be included in Release 7

...

High Level Overall Requirements
CI, Blueprint Validation Lab Sub-Committee Requirements
1. Present Pod Topology document.
2. Peering w/LF Jenkins - (Note: peering is an optional requirement)
3. Push logs through Nexus. (Note: This is mandatory for Incubation self-certified and Maturity)
4. Usage of topics for release
  1. Releases >= 1.0 (e.g. 1.xyz, 2.xyz etc) are reserved for BP that have been approved as Core by the TSC (considered ‘GA’ quality).
  2. Releases <1.0 (e.g. 0.xyz etc) are reserved for projects that have not reached the Akraino Core level (i.e. anything that is in Incubation (‘alpha’ quality) and Mature (‘beta’ quality).
5. Enforcement of Static Code Analysis through SonarCloud (SaaS), WIP LF Release Engineering & Security Subcommittee. (Note: This is an optional requirement for Incubation self certified and mandatory for Maturity)
Security Sub-Committee Requirements, please fill in Release 4 Blueprint Scanning Status. Instructions can be found at: Steps To Implement Security Scan Requirements
Blueprint Validation Framework Feature Project Requirements See TSC meeting.
Projects going for Maturity Review please refer to Maturity Criteria defined by Process subcommittee BP Graduation Review Processes and Criteria (Note this is not required for self certification, only required for maturity review)
Documentation Sub-Committee Requirements
User Documents:
The following documentation with the following sections called out should be on the wiki with links to rest of the sections as applicable. We prefer that the entire doc is on the wiki but we do not require it.
Architecture - Blue print Overview and overall architecture
Release Notes – Summary and What is released
Installation Doc – Introduction and deployment architecture
Test Document – Introduction and Overall Test Architecture
Developer Documents:
We are also recommending that Blueprints include via ReadtheDocs, with each Blue Print given their own repo, but we do not require it
API Sub-Committee Requirements (Note: See this link for requirements: Blueprint Projects API Reporting Requirements)
Community Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity)
Process Sub-Committee Requirements (Note: See the Process Sub Committee page defining the TSC approved Maturity review process and requirements for those requesting inclusion in R3 at Mature level BP Graduation Review Processes and Criteria)
Upstream Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity). Here is the R6 release Upstream BP review status Release 6 Upstream Review Status, Release Upstream Compliance. Also please refer to the page for the R6 requirement as well.