Versions Compared

Old Version 5

changes.mady.by.user Haibin Huang

Saved on

compared with

New Version Current

changes.mady.by.user Bin Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The following items are expected to be completed for the project to Pass the M4 Code Freeze Milestone.

M4 Release Code Freeze Milestone overview is available in wiki.


Info
titleUsage
  1. Use the "Copy" option (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?
Product ManagementHave all JIRA Stories supporting the release use case been implemented?yes
By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are implemented in Amsterdam Release. (Example

Jira Legacy
serverSystem Jira
jqlQueryproject =

aai and type=Story and fixversion="Amsterdam Release"

MULTICLOUD AND issuetype = Story AND status in (Closed, Submitted, Delivered) AND fixVersion = "Casablanca Release" ORDER BY status ASC, created DESC
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

for AAI project, edit for your project)

For each JIRA story that are implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Amsterdam Release"
List the Stories that will not be implemented in this current
Release.By using the macro JIRA Issue/Filter, provide a link to JIRA in listing the stories that are NOT implemented in Amsterdam
Release.
(Example

Jira Legacy
serverSystem Jira
jqlQueryproject =

aai and type=Story and fixversion="Beijing Release"

MULTICLOUD AND issuetype = Story AND status in (Open, "In Progress", REOPENED) AND fixVersion = "Casablanca Release" ORDER BY status ASC, created DESC
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

for AAI project, edit for your project)

For each JIRA story that will not be implemented in Amsterdam Release, you have to setup in JIRA the JIRA fixVersion="Beijing Release"

Are committed Sprint Backlog Stories been coded and marked as "Closed" in Jira?
Provide Link to Project backlog
Yes

Jira Legacy
serverSystem Jira
jqlQueryissueKey in (MULTICLOUD-19,MULTICLOUD-250,MULTICLOUD-251,MULTICLOUD-260,MULTICLOUD-261,MULTICLOUD-264,MULTICLOUD-276,MULTICLOUD-288,MULTICLOUD-324,MULTICLOUD-326,MULTICLOUD-335,MULTICLOUD-337,MULTICLOUD-356,MULTICLOUD-361)
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


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

Release ManagementHave all issues pertaining to FOSS been addressed?N/A

Have all findings from previous milestones been addressed?YesList previous milestone issues that have not been addressed.For M2 and M3 Milestones, ensure all findings have been closed.

Has the Project Team reviewed and understood the most recent license scan reports from the LF, for both (a) licenses within the codebase and (b) licenses for third-party build time dependencies?

Yes

For both (a) and (b), have all high priority non-Project Licenses been either removed or escalated as likely exception requests?Yes

DevelopmentAre all Defects of priority Highest and High in status "Closed" in Jira?Yes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-344
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-334

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-296
Jira LegacyserverSystem JiraserverId

4733707d-2057-3a0f-ae5e-4fd8aff50176keyMULTICLOUD-295

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-284

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-275
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-272
Jira LegacyserverSystem JiraserverId4733707d-2057-3a0f-ae5e-4fd8aff50176keyMULTICLOUD-271

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-250
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-249
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyMULTICLOUD-232


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

Goal: 50% for Incubation project in

Beijing

Casablanca Release

https://sonar.onap.org/projects?search=multicloud&sort=-analysis_date

For evidences, provide link(s) to Gerrit repos by providing the URL as shown in this example

Example

Is there any binaries (jar, war, tar, gz, gzip, zip files) in Gerrit project repository?No
Refer to CI Development Best Practices
Is there any pending commit request older than 36 hours in Gerrit?No

Provide the "% Achived" on the CII Best Practices program.100%https://bestpractices.coreinfrastructure.org/en/projects/1706As documented in CII Badging Program, teams have to fill out CII Best Practices

Is there any Critical and Severe level security vulnerabilities older than 60 days old in the third party libraries used within your project unaddressed?

Nexus-IQ classifies level as the following:

  • Critical is level 7 to 10
  • Severe is level 4 to 6
  • Moderate is level 1 to 3

which is complaint with CVSS V2.0 rating.

NoIn the case critical known vulnerability are still showing in the report, fill out the
Security/Vulnerability Threat Template
/wiki/spaces/SV/pages/16089093 in your project.Ensure 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 (verify + merge jobs)?
No
Yeshttps://jenkins.onap.org/view/multicloud
Have all OOM Staging Healtcheck related to your project passed?
No
Yes

http://onapci.org/jenkins/job/windriver-oom-staging-daily/86/console


Are all snapshot binaries available in Nexus-staging?Yeshttps://nexus.onap.org/#nexus-search;quick~multicloud
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0?Yes
Contact the upstream teams to make sure they will release their artifacts (in Nexus Release repo) so you can build by depending on these released artifacts by RC0.
Integration and TestingHave 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins?
No
YesAll jobs pertaining to your project MUST pass
Is there a Docker images available for your project deliverable?

Yes

https://nexus3.onap.org/#browse/search=keyword%3Dmulticloud
Has the project code successfully passed the Daily Build process?
No
Yes
Goal is to ensure the latest project commit has not broken the Integration Daily Build 
DocHas the team created a docs folder and Development and Release Notes documentation templates in Readthedocs?Yeshttps://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/index.html

Documentation Team is using Readthedocs for documenting user facing documentation.

ReadTheDcos shall be considered as a starting point for someone new within ONAP.

The ReadTheDocs is the ONAP Documentation facade visible to users.

Link to http://onap.readthedocs.io/en/latest/guides/onap-developer/how-to-use-docs/include-documentation.html#templates-and-examples

How to setup the template for my project?

Is the API documentation section populated?Yes
Setup MultiCloud Development Env
https://onap.readthedocs.io/en/latest/submodules/multicloud/framework.git/docs/MultiCloud-API-Specification-V1.htmlEnsure there is at least a direct link toward the API documentation which may be already existing in the wiki.