The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.
M3 Release Architecture Milestone overview is available in wiki.
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||
|---|---|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | planned for 8/22Yes | APPC Presentation | Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough. | ||
| Is there a plan to address the findings the API review? | TBD | Link to plan | The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki | N/A | See Note | Note: There were no findings coming out of the API review meeting; however, there is an item being addressed between MultiVIM and CDP-PAL around https support that needs to be resolved. CDP-PAL uses https, MultiVIM currently does not support it - both teams investigating to determine which solution would be most feasible in the short time we have. Update 8-22-17: Per CDP-PAL, they can support http, so at this stage, we have a plan forward. |
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Yes | NA | In the case some changes are necessary, bring the request to the TSC for review and approval. | |||
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | Yes | If Yes, please a link to the evidence of these changes. | Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes. Two key items have increased the scope from what was understood at M1: | |||
| Provide link to the API Documentation. | Yes | |||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | Provide Link to Project backlog | |||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | APPC JIRA Board | ||||
| Have all findings from previous milestones been addressed? | In-ProgressYes | Provide link to JIRA findings | ||||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | No, work In-Pogress | Goal: 30-50% for Incubation project | Guidance on Code Coverage and Static Code Analysis | ||
| Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | Provide link to evidence | APPC Gerrit | |||
| Are all binaries available in Nexus? | Yes | Provide link to evidence | APPC Snapshot on Nexus | |||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | No. In ProgressYes | Provide link to evidence | |||
| Has the project code successfully passed the Daily Build process? | Yes | Goal is to ensure the latest project commit has not broken the Integration Daily Build |