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.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | The api review did happen last week (8/15) between Ron and Chris Donley (from Architecture team) | 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? | No | API review concluded that there were no issues | 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 | 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? | No | 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. | |
| Provide link to the API Documentation. | N/A | we don't expose api but uses api's from other project (policy, dcae and sdc) | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | Link to Project backlog | |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Link to CLAMP R1 board in JIRA | ||
| Have all findings from previous milestones been addressed? | Yes | Design stories have captured the changes | Still some design unknowns, but they are minor now, we will cope with them under improvement tasks in next sprint | |
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 30-50% for Incubation project | CLAMP alone does 31.5% |
| Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | link to CLAMP Jenkins project tab | ||
| Are all binaries available in Nexus? | Yes | link to Nexus project folder | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | link to CSIT Jenkins tab | System Integration testing is running for CLAMP |
| Has the project code successfully passed the Daily Build process? | Yes | link to Jenkins Clamp tab | Goal is to ensure the latest project commit has not broken the Integration Daily Build |