| MBI0 | Blue Print Kick Off | The project is defined and approved by TSC vote to enter incubation stage (Incubation Review) |
| MBI1 | First regular community call held | Recurring meeting should have been setup and details appear in the BP community meeting calendar: https://lists.akraino.org/g/blueprints/calendar. The first meeting date would be the timestamp for the 'Achieved date'. |
| MBI2 | Planning complete | MBI2 is dependent on MBI1 - Projects that have successfully completed MBI1, must complete their planning, including scenario or deliverable definition.
- As part of the planning process, all projects will complete a project planning template.
- hardware set up definition frozen
- Identify team working on features & testing
- Peer Jenkins Set up
|
| MBI3 |
Integration Test plan created and shared with the community Requirement/ Feature Freeze (if applicable)
| MBI3 is dependent on MBI1 - Requirement/Feature freeze if there is code contribution as part of the blueprint or the upstream (All features are identified and JIRA stories created)
- Comprehensive test plan documentation is created
- hardware set up definition frozen ( NS)
- Document the lab setup required and identify the labs that would be used to test this blueprint. If the lab is third party lab, get the lab reserved.
- Security:<TBF>
|
| MBI4 | Scripts development and Set up accessible AW: What are these scripts? Lab is set up for CD | - Make scripts available to create setups in third party labs.
- Make the setups accessible for everybody (optional) - AW: must be available to community if part of BP)
- Instructions to access the setups. Method to reserve/un-reserve setups. Preferably two setups at-least. (AW: What does two setups mean?)
- All HW required to deploy the BP has been installed and is ready to start CD of actual BP
- Security: <TBF>
|
| MBI5 | Code Freeze (if applicable) Additional test case development complete
| - Integration complete of all SW packages that are part of the blueprint (In case of CI this waterfall approach is optional)
- All additional test cases beyond those defined as mandatory for each layer being deployed by the BP are automated (AW: not all additional testing must be automated) and made them available in blueprint repos.
- Make the images available in public repository (Nexus?) and create scripts necessary to install all SW packages in various sites as identified by blueprint (In case of CI this waterfall approach is optional)
|
| MBI6 | First deployment in validation lab First testing logs shipped | - All requirements uptill MB4 should be complete at this stage
- 1st run of test cases and rest results logs automatically posted to LF CI servers
- All test cases planned for the release have been executed
- Test results published
- (In case of CI / CD this waterfall approach is optional)
- Failures and other issues have been documented
|
| Ad hoc reporting | | |
| MBI6 | CI/CD based testing Critical issues fixed. Documentation complete (for third parties to recreate setup and run the tests) | - Complete the documentation
- Critical issues fixed
|
| Sign-Off | Release | Project graduate to Mature stage |