DRAFT PROPOSAL FOR COMMENTS
The following items are expected to be completed for the project to Pass the Release Candidate Milestone.
This template must be filled out for every Release Candidate Milestone (RC0, 1, 2, x)
RC Release Candidate Milestone overview is available in wiki.
Info | ||
---|---|---|
| ||
|
Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product Management | Are all tasks associated with the release been marked as "Done" in Jira?Yes | No | One pending:
| ||||||||||||||||||||||||
Have all findings from previous milestones been addressed? | No | One of our CSIT job is still failingYes | |||||||||||||||||||||||||
Development | Have all Defects of priority Highest and High been in status "Done" in Jira? | NoYes | One pending
| ||||||||||||||||||||||||
jqlQuery | project="OPTFRA" and issueType="Bug" and fixVersion="Beijing Release" and Status != "Closed" AND Priority in (High, Highest) | count | true
|
|
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/
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.
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-osdfmusic/
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/https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-release-version-java-daily/music/
Being used internally within OOF and Portal, so no separate OOM deployment.
Pending review from OOM team. Our team committed the changes for review on 04/08.
For RC0, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template?
music.git docs folder exists with templates as shown here.
http://docs.onap.orgWe have the file structures in readthedocs and have been populating content in it (https://onap.readthedocs.io/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 | ||||||
---|---|---|---|---|---|---|
|
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=defaultWe plan to make progress on this and get it ready by RC1.
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?