Versions Compared

Old Version 4

changes.mady.by.user Former user

Saved on

compared with

New Version 5

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?

Link to JIRA

Jira Legacy
serverSystem Jira
columnskey,summary,type,status,resolution
maximumIssues20
jqlQueryproject = MSB and type != bug and fixVersion = "Amsterdam Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176



Have all findings from previous milestones been addressed?Yes

Provide link to JIRA findings

Jira Legacy
serverSystem Jira
columnskey,summary,type,status,resolution
maximumIssues20
jqlQueryproject = MSB and type = bug and createdDate < "2017/10/01"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?Yes

Provide link to JIRA issue (type bug) of priority Highest and High. 

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = MSB and priority in(High,Highest) and type = bug
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Are all JIRA issues used as a reference in a commit in status "Done" in Jira?Yes


Very often, some JIRA issue remains in status "Todo" in JIRA while the commit they are referenced to is successful.
Is there any pending commit related to Highest and High priority issues older than 36 hours in Gerrit? In case there are messages going back and forth between authors and reviewers, it is acceptable to be above 36 hours.No

Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Provide link to "Merge job" as evidence in Jenkins project tab

MSB Jenkins Jobs

Sometimes Jenkis jobs due to CI/CD or Sonar system reason. It seems that the ONAP IT Infrastructure is not stable recently.


Has the team delivered all their release artifacts in Nexus Release or Nexus Staging repo?

There should be at least ONE version of each artifacts available in Nexus Release or Nexus Staging repo.

YesMSB BinariesRefer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?Yes

Provide link to evidence. As things are moving fast, we want to ensure CSIT are still "green".

MSB CSIT jobs


Is there a Docker images available for each repository?Yes

Provide link to evidence

ONAP Docker Repo


Has the project code successfully passed the Daily Build process?Yes

MSB Jenkins Jobs

Sometimes Jenkis jobs due to CI/CD or Sonar system reason. It seems that the ONAP IT Infrastructure is not stable recently.

Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Documentation

For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?




Most teams have already created the high level file structures in readthedocs, and populated some actual documentation. However, the remaining sections of the appropriate teamplate must be completed.

Platform: A&AI, APP-C, CLAMP, CLI, DCAE, DMaaP, Holmes, MSB, OOM, Policy, Portal, SDN-C SDC, SO, UseCase UI, VFC, VID

SDKs: AAF, CCSDK, External API Framework, Multi VIM/Cloud, VNFSDK

For RC1, has the team addressed any issue (recorded in JIRA) provided by the Documentation team?




For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate?




For RC2, has the Documentation Team provided the final approval for your project documentation?