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)? | 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?Link to plan | N/A | No APIs | The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki. | |
Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Yes | N/ANA | 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? | No | The OOM has been working with the project teams to integrate them into OOM as described @ M1If 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. | |
Provide link to the API Documentation. | N/A | |||
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | No | See our Epic Report and Sprint Planning Board Provide Link to Project backlog | |
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | No | |||
Have all findings from previous milestones been addressed?Provide link to JIRA findings | N/A | |||
Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | Goal: 50% for Incubation project in Beijing | Guidance on Code Coverage and Static Code Analysis |
Is there any pending commit request older than 36 Business hours in Gerrit? | See search | |||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | N/A | No violations see report | Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. | |
Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Provide link to evidenceN/A | |||
Are all binaries available in Nexus? | Provide link to evidenceStretch goal for R2 | |||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | N/A | OOM is used for CD - see: Auto Continuous Deployment via Jenkins and KibanaProvide link to evidence | |
Has the project code successfully passed the Daily Build process? | N/A | OOM is used for CD - see: Auto Continuous Deployment via Jenkins and Kibana | Goal is to ensure the latest project commit has not broken the Integration Daily Build |