Page History

...

1. High Level Overall Requirements
2. CI, Blueprint Validation Lab Sub-Committee Requirements
   1. Present Pod Topology document.
   2. Peering w/LF Jenkins.
   3. Push logs through Nexus.

   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.

3. Security Sub-Committee Requirements
4. Blueprint Validation Framework Feature Project Requirements
5. Documentation Sub-Committee Requirements
6. API Sub-Committee Requirements
7. Community Sub-Committee Requirements
8. Process Sub-Committee Requirements
9. Upstream Sub-Committee Requirements

...