Versions Compared

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?YesNo

One pending:


Jira Legacy
jqlQuery
serverSystem Jiraproject = optfra AND (issuetype = task OR issuetype = Sub-task) AND (status = DONE or status = implemented) AND fixVersion = "Beijing Release"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
marked Done

Jira Legacy
serverSystem Jira
jqlQueryproject = optfra AND (issuetype = task OR issuetype = Sub-task) AND (status != DONE and status != implemented) AND fixVersion = "Beijing Release"
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
pending, but are tasks associated with S3P or integration testing

keyMUSIC-70



Have all findings from previous milestones been addressed?NoOne of our CSIT job is still failingYes

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

One pending

Jira Legacy
serverSystem Jira

jqlQueryproject="OPTFRA" and issueType="Bug" and fixVersion="Beijing Release" and Status != "Closed" AND Priority in (High, Highest)
counttrue
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

marked Done

keyMUSIC-70



Are all JIRA issues used as a reference in a commit in status "Done" in Jira?Yes
We believe our team has marked tasks as Done when the commit is made - not sure how to verify this though.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

https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-verify-java/

https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-verify-python/

https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-verify-java/

https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-verify-python/

https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-merge-java/

https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-merge-java/

music/


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.

YesStaging repo: https://nexus.onap.org/content/repositories/staging/org/onap/optfmusic/Refer to Independent Versioning and Release Process for procedureIntegration and TestingHave all CSIT Use Cases (created by each project team) passed?NoYes

Passing:

https://jenkins.onap.org/view/optf/job/optf-has-master-csit-has/

https://jenkins.onap.org/view/optf/job/optf-has-master-verify-csit-has/

Failing:

https://jenkins.onap.org/view/optf/job/optf-osdf-master-csit-osdf/

music/


Is there a Docker images available for each repository?YesHas the project code successfully passed the Daily Build process?Yes*

Two of our release jobs have failed yesterday, but was successful before then. Our team is working on identifying the issue here.

jenkinsviewoptf/job/optf-has-master-conductor-docker-java-version-shell-daily/

https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-docker-java-version-shell-daily/

https://jenkins.onap.org/view/optf/job/optf-has-master-conductor-release-version-java-daily/
Has the project code successfully passed the Daily Build process?Yes

https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-release-version-java-daily/music/

Goal is to ensure the latest project commit has not broken the Integration Daily Build Has the OOM deployment passed?No

Pending review from OOM team. Our team committed the changes for review on 04/08.

https://gerrit.onap.org/r/#/c/41495/

NA

Being used internally within OOF and Portal, so no separate OOM deployment.


Has the Heat deployment passed?NoOur team is currently working with the Integration team (Marco Platania)NABeing used internally within OOF and Portal, so no separate OOM deployment.
Documentation

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

NoWe have the file structures in readthedocs and have been populating content in it (https://onap.readthedocs.io


Yes


music.git docs folder exists with templates as shown here.

http://docs.onap.org/en/latest/submodulesguides/optf/has.git/docs/index.html). We also have the the required content in the Wiki (architecture, API, Deployment instruction etc).

Our team is working on converting our existing documentation into the required format as a part of the S3P usability user story:

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyOPTFRA-41
.

We plan to make progress on this and get it ready by RC1.onap-developer/developing/index.html#music

Section templates for music are referenced from these in the documentation index

http://docs.onap.org/en/latest/search.html?q=music&check_keywords=yes&area=default


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?

NA

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

NA

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