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)? | Yes | Architecture API | 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? | NA | 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. | Yes | in | |||||||||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | Provide Link to Project backlog Team using Kanban | SO-Jira | |||||||
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | NA | As the team is using a Kanban approac,there is no Sprint.Yes | SO-Jira | ||||||||
| Have all findings from previous milestones been addressed? | Yes | ||||||||||
| Development | Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||||||||
| Do you have a plan to address by M4 the Critical and High vulnerabilities in the third party libraries used within your project? | Yes |
Critical would be addressed and high would be checked on need basis | 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)? | Yes | Jenkins VNFSDKSO | |||||||||
| Are all binaries available in Nexus autorelease? | Yes | ||||||||||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | Yes | Jenkins VNFSDKSO | ||||||||
| Has the project code successfully passed the Daily Build process? | Yes | Jenkins VNFSDKSO | Goal is to ensure the latest project commit has not broken the Integration Daily Build |