Release 3 target date is May 30th 2020.  

1. Self Certified Milestones Achievement Due Date Apr 30th 2020 ( Milestone 4) 

2. Maturity Review Milestone Achievement  Due date Apr 30th 2020

Please add targeted and achieved R3 milestones at:

BP Incubation Stage Reporting R2 (To be updated)

Define area of focus

(to be updated)

1. Virtual meeting to start to have a session to discuss all of the agenda items.
2. Different patches from different blueprints need to be up-streamed.
3. Need a consistent framework
4. New blueprints have been committed for R3.
5. Want to increase standards on Release 3.
6. Validation Project test layers and test cases
7. Incubation Self Certification in R3?

Release 3 Requirements

1. High Level Overall Requirements
2. 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)

3. Security Sub-Committee Requirements for Maturity Review Approved by TSC July 11, 2019，please fill in Security Scan Status (Note this is not required for self certification, only required for maturity review)
4. Blueprint Validation Framework Feature Project Requirements See TSC meeting and Slides
   
5. 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)
6. 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

7. API Sub-Committee Requirements  (Note: no mandatory requirements for Incubation self-certified or Maturity)
8. Community Sub-Committee Requirements  (Note: no mandatory requirements for Incubation self-certified or Maturity)
9. 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)
10. Upstream Sub-Committee Requirements (Note: no mandatory requirements for Incubation self-certified or Maturity)

Blue Prints Participating in Release 3

Internal Target date to meet Rel 3 Criteria is Apr 30th ( please add your target/achieved date at the BP Incubation Stage Reporting R2)

(To be updated)

03/02~03/2020 Akraino TSC F2F & 2020 Planning meeting