Skip to end of metadata
Go to start of metadata

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 AreaCheckpointYes/NoEvidencesHow to?
Architecture


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

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?YesLink to planThe 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?YesNAIn 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?

NoIf 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.YesVF-C APIs
Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?Yes

Provide Link to Project backlog

VF-C backlog


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

Have all findings from previous milestones been addressed?YesProvide link to JIRA findings
DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)

WIP

Only one component haven't reach 50%

Goal: 50% for Incubation project in Beijing

VF-C sonar data

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

WIP


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)?YesVF-C Jenkins
Are all binaries available in Nexus?YesVF-C binaries in Nexus
Integration and Testing

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

YesVF-C Jenkins
Has the project code successfully passed the Daily Build process?YesVF-C JenkinsGoal is to ensure the latest project commit has not broken the Integration Daily Build