...
- High Level Overall Requirements
- CI, Blueprint Validation Lab Sub-Committee Requirements
- Present Pod Topology document.
- Peering w/LF Jenkins.
- Push logs through Nexus.
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).
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).
Enforcement of Static Code Analysis through SonarCloud (SaaS), WIP LF Release Engineering & Security Subcommittee.
- Security Sub-Committee Requirements Approved by TSC July 11, 2019
- Blueprint Validation Framework Feature Project Requirements
- 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 Blue prints include via ReadtheDocs, with each Blue Print given their own repo, but we do not require it
- API Sub-Committee Requirements
- Community Sub-Committee Requirements
- Process Sub-Committee Requirements
- Upstream Sub-Committee Requirements
Blue Prints Participating in Release 2
| Project Name | Part of Release1? | MBI0 Project Induction Date | Achieved/Target date | MBI1 Kick Off | MBI2 Planning process Defined | MBI3 CD Test Scripts developed 1st Validation Lab is Set up | MBI4 First Full CD deployment BP is ready to download and deployable by users as self certified | Going for Maturity Review? |
|---|---|---|---|---|---|---|---|---|
| View file | ||||
|---|---|---|---|---|
|
...