Versions Compared

Key

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

...

AAI-1127Yes
Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre all tasks associated with the release been marked as "Done" in Jira?NoStill have to release artifacts; Yes

Jira Legacy
key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverSystem Jiracolumns
jqlQueryproject = "Active and Available Inventory" and fixVersion != "Casablanca Release" and status != Closed
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1127



Have all findings from previous milestones been addressed?YesProvide link to JIRA findings
DevelopmentHave all Defects of priority Highest and High been in status "Done" in Jira?No

Jira Legacy
key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionAAI-1127
serverSystem Jiracolumns
jqlQueryproject = "Active and Available Inventory" and fixVersion = "Beijing Release" and type = "Bug" and status != Closed
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176key


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

Jira Legacy
key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverSystem Jiracolumns
jqlQueryproject = "Active and Available Inventory" and fixVersion != "Casablanca Release" and status != Closed
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyAAI-1136

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

YesVery 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.NoAAI in Gerrit
Are all the Jenkins jobs successfully passed (verify + merge jobs)?Yes

Jenkins Merge Jobs

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


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.

No - WIP to get fully releasedWaiting on
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
key


Refer to Independent Versioning and Release Process for procedure
Integration and TestingHave all CSIT Use Cases (created by each project team) passed?YesJenkins CSIT
Is there a Docker images available for each repository?Yesnexus3.onap.org:10001
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 
Has the OOM deployment passed?YesEnsure in Jenkins External Labs all Health Check pass.
Has the Heat deployment passed?YesEnsure in Jenkins External Labs all Health Check pass.
Documentation

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


Yes

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?

N/A

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

WIP

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