The Smart Cities blueprint is requesting maturity review for Akraino release 6.
This page references the requirements in BP Graduation Review Processes and Criteria specifically the table cell for Incubation -> (Mature) on the second row from the bottom of the page.
- Validation lab check:
- Multiple Jenkins jobs exist for deploying AI Edge to multiple Lab and for otestack installation and various testing. The jobs listed below are the primary CD jobs. Additional job logs can be viewed on Nexus, but these listed here are the relevant ones for Akraino maturity review.
- Myais
- Release inclusion check:
- Release 5 Planning --1st participation in Release 5 in the incubation stage.
- Release 6 Planning --2nd participation in Release 6 in the incubation stage.
- SW quality/functional check:
The SW quality will be assessed as reaching beta according to :
- Passing the mandatory set of test cases for all deployed layers using the tools and test set for each layer as defined by the Akraino Validation Framework Validation feature project (Akraino Blueprint Validation Framework) (after TSC approval). This will define minimum mandatory set of test that must be passed for each layer included in BP, plus
- Passing any additional test cases defined by the specific BP project as mandatory, plus
- Achieving the minimum Security requirements as defined by the Security subcommittee Steps To Implement Security Scan Requirements
- HW definition check:
Precise HW requirements and descriptions are defined and included in the BP's documentation (as used in both lab validations)
- Upstream dependencies check:
Upstream dependencies must be clearly defined
- Documentation check:
Documentation subcommittee to provide a recommendation on graduation, or if not with items requiring action/remedy.
This check includes verification that any supported APIs are clearly documented
- Community Health and Stability check:
PTL should provide a summary of contributors and committers and companies and demonstrate growth - Project is active and contributes to Akraino: The project demonstrates increasing number of commits and/or number of contributions across recent releases. Contributions are commits that have been to an Akraino repository project or related upstream project. Commit examples can be patches to update the requirements document of a project, code addition to an Akraino or upstream project repository, new additional test cases and so forth. [maybe create a template, or use something like Bitergia to get some consistent metrics coming into this review].
The PTL should demonstrates stable output (code base, documents) within its history of releases in accordance with the release policy.