Akraino project reporting provides visibility of the each BP validation project (MBx1, MBx2 etc) and feature project (MF1, MF2 etc) by means of a set of defined milestones terms MB1, MB2 etc.
The milestones are defined by the Documentation subcommittee.
Recording the milestones will be done by each project PTL so that the TSC can track project status.
1) Entry Criteria: The project is approved to enter the incubation stage as per the TSC guideline (Akraino Project Reviews)
2) All milestones below may not apply to all projects and hence some may be marked optional after approval from TSC
3) Details of the Blue Print Milestones are in table below at the bottom of the page
4) There are sequential milestones (S) and non sequential milestones (NS). The non sequential milestones are guidelines to be completed at a certain stage, however they are not gating factors to enter the next stage. However the NS milestones also need to be completed at some point which will be marked as part of the relevant stage.
...
Project Name
...
MB0 Kick-Off
...
MB1
Planning complete
Identify integration/developers team & testing team
...
MB2
Integration Test plan created and shared with the community
Requirement/Feature Freeze (if applicable)
MB3
Scripts development and Set up accessible
Lab is set up for CD
...
MB4
Code Freeze (if applicable)
Test case development complete
...
MB5
first deployment in validation lab
first testing logs shipped
...
MB6
CI/CD based testing
Critical issues fixed.
Documentation complete (for third parties to recreate setup and run the tests)
...
Sign-Off (April 30th)
Release moved to mature
(Decision of completion made by PTL and TSC)
...
...
...
...
...
...
...
...
...
...
...
...
Project Name
...
M0 Kick-Off
...
M1
Planning
...
M2
Functionality freeze
...
M3
API Freeze
...
M4
Code Freeze
...
RC0
Release Candidate 0
...
RC1
Release Candidate 1
...
RC2
Release Candidate 2
...
Sign-Off
Release Delivery
...
Project Name
...
M0 Kick-Off
...
M1
Planning
...
M2
Functionality freeze
...
M3
API Freeze
...
M4
Code Freeze
...
RC0
Release Candidate 0
...
RC1
Release Candidate 1
...
RC2
Release Candidate 2
...
Sign-Off
Release Delivery
...
...
...
...
...
MS
...
Name
...
Description/Checklist
...
- Projects that have successfully completed MS0, 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 (NS)
- Identify team working on features & testing (NS)
- Paid Jenkins Set up (NS)
...
Integration Test plan created and shared with the community
Requirement/ Feature Freeze (if applicable)
- 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>
...
Scripts development and Set up accessible
...
- Make scripts available to create setups in third party labs.
- Make the setups accessible for everybody (optional).
- Instructions to access the setups. Method to reserve/un-reserve setups. Preferably two setups at-least.
- Security: <TBF>
...
Code Freeze (if applicable)
Test case development complete
- Integration complete of all SW packages that are part of the blueprint
- All test cases are automated and made them available in blueprint repos.
- Make the images available in public repository (Nexus?) and create scripts to necessary to install all SW packages in various sites as identified by blueprint
Blueprint Validation Project reporting
BP validation projects milestones will be different in the 'Incubation' and 'Mature' stages since the graduation criteria from these two stages are different.
A single table shall be maintained for all projects in Incubation (i.e. tracking the progress towards graduating from Incubation to Mature)
A single table shall be maintained for all project in Mature stage (i.e. tracking the progress towards graduating Mature to Core)
Each BP validation project's PTL is responsibility for updating the Incubation or Mature BP tracking tables for their BP validation project so that the TSC can easily track all BP validation projects' status.
In addition to the PTLs reporting the actual dates each milestone is achieved, the PTLs are encouraged in their planning stage to enter their target date for each milestone in the same table.
Feature Project reporting
Each feature project's PTL is responsibility for the updating feature project tracking table for their feature project so that the TSC can easily track all feature projects' status.
Blueprint Projects R4 API Information Reporting Requirements
Starting with R4, all blueprint projects are required to report significant edge computing APIs they both expose and consume. The API Subcommittee page has instructions
...
first deployment in validation lab
first testing logs shipped
...
- All requirements uptill MB4 including NS ones should be complete at this stage
- 1st run of test cases and results shared
- All test cases planned for the release have been executed
- Test results published
- Failures and other issues have been documented
...
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
...
.