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.
Usage
- Copy and Paste this template in the wiki Space along with your Release document
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
| 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 | 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? | 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, resources, API, repositories since M1 milestone? | If Yes, please a link to the evidence of these changes. | |||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Provide Link to Project backlog | ||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | ||||
| Have all findings from previous milestones been addressed? | Provide link to JIRA findings | |||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Goal: 50% for Incubation project | Guidance on Code Coverage and Static Code Analysis | |
| Is there any pending commit request older than 24 hours in Gerrit? | ||||
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Provide link to evidence | |||
| Are all binaries available in Nexus? | Provide link to evidence | |||
| Integration and Testing | Have 50 % of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? | Provide link to evidence | ||
| Have you reviewed all the CSIT Test Case with Integration Team? | Schedule a meeting with Integration Team to review the deliverable. | |||
| Has the project code successfully passed the Daily Build process? | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |||