Practice Area | Checkpoint | Yes/No | Evidences | How to? |
---|
Product Management | Have all JIRA Stories supporting the release use case been implemented? |
NocolumnsmaximumIssues | 20 |
---|
key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | jqlQuery | project = MSB and status = done and fixVersion = "Amsterdam Release" and issuetype != Bug |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 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. | Yes | Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project = |
---|
|
|
Holmes MSB and fixVersion = "Beijing Release" | count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
| 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 "Done" in Jira? |
NoYes |
|
|
Are all tasks associated with committed Sprint Backlog Stories been marked as "Done" in Jira? |
NoYes |
|
|
Release Management | Have all issues pertaining to FOSS been addressed? | Yes |
|
|
Have all findings from previous milestones been addressed? | Yes |
| For M2 and M3 Milestones, ensure all findings have been closed. |
Development | Are all Defects of priority Highest and High in status "Done" in Jira? | Yes | Jira |
---|
server | ONAP JIRA |
---|
jqlQuery | project = MSB and priority in(High,Highest) and type = bug |
---|
count | true |
---|
serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
---|
|
|
key | HOLMES-64Holmes 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. |
|
Are all snapshot binaries available in Nexus? | Yes |
Holmes MSB Binaries |
|
Do you have a clear plan to implement the Independent Versioning and Release Process by RC0? | Yes | This is supposed to be done by RC0. | 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 Testing | Have 100% of Continuous System Integration Testing (CSIT) Use Cases been implemented successfully in Jenkins? | Yes | All jobs pertaining to your project MUST pass |
|
Is there a Docker images available for your project deliverable? | Yes | ONAP Docker Repo |
|
Has the project code successfully passed the Daily Build process? | Yes |
Sometimes they may fail due to the environment failures of the CI/CD platform, not actually caused by the Holmes teamThe directories are created. The API documents are converted as required by the doc team. But now we are not able to find our page on 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 |
Doc | Has the team created a docs folder and Development and Release Notes documentation templates in Readthedocs? |
No | . Still woring with the doc team to chech what the problem is.But generally speaking, the doc process is now under control and we'll catch up very soon.
See above.