MSB Deliverables for API Freeze Milestone Checklist-M3

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

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.

  2. Fill out the Yes/No column

  3. Provide link to evidence (when necessary)

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Architecture



Has the Project team reviewed the APIs with the Architecture Committee (ARC)?

Yes

MSB R2 Architecture Review

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?

Yes

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?

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

Microservice Bus API Documentation



Release Management

Are committed Sprint Backlog Stories been marked as "Done" in Jira board?

Yes

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=25&projectKey=MSB&view=planning.nodetail



Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?

Yes

https://jira.onap.org/secure/RapidBoard.jspa?rapidView=25&projectKey=MSB&view=planning.nodetail



Have all findings from previous milestones been addressed?

Yes

Getting issues...



Development

Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)

Yes

https://sonar.onap.org/dashboard?id=org.onap.msb.discovery%3Amsb-discovery-parent

https://sonar.onap.org/dashboard?id=org.onap.msb.apigateway%3Amsb-apigateway-parent

https://sonar.onap.org/dashboard?id=org.onap.msb.swagger-sdk%3Aswagger-sdk

https://sonar.onap.org/dashboard?id=org.onap.msb.java-sdk%3Amsb-java-sdk

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

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  vulnerabilities in the third party libraries used within your project?

Yes



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

https://jenkins.onap.org/view/msb/



Are all binaries available in Nexus?

Yes

maven lib: https://nexus.onap.org/#nexus-search;quick~msb

docker: https://nexus3.onap.org/#browse/search=keyword%3Dmsb



Integration and Testing


Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins?

Yes

https://jenkins.onap.org/view/msb/



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 



please  [pli?z]  ??X

????

int. ???????

vt. ???????????

vi. ?????????

????

Please: ?

please hurry: ???

please killall: ??????