DRAFT PROPOSAL FOR COMMENTS
The following items are expected to be completed for the project to Pass Release Sign-Off Milestone.
Release Sign-Off Milestone overview is available in wiki.
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Product Management | Are committed Product Backlog Stories been coded and marked as "Closed" in Jira? | Yes | ||
| Are all tasks associated with committed Product Backlog Stories been marked as "Closed" in Jira? | Yes* | AAF has several tickets about Certs listed as AAF errors, but these are not AAF problems. Tickets are in pre-close mode waiting to hear from Integration before final close. | ||
| Provide the project features list under the form of a bulleted list. | Yes | https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/release-notes.html | ||
Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off | N/A | |||
| Release Management | Have all issues pertaining to FOSS been addressed? | Yes | Source code has Headers according to FOSS. We use no Source Code copy. | Rules for implementing FOSS in a project |
| Have all findings from previous milestones been addressed? | N/A | |||
| Development | Are all the Jenkins jobs successfully passed (verify + merge jobs)? | Yes | https://jenkins.onap.org/view/aaf/ | https://jenkins.onap.org/view/Merge-Jobs/ |
| Are all binaries available in Nexus Release repository? | Yes | https://nexus.onap.org/#nexus-search;quick~org.onap.aaf.authz | ||
| Are all Docker images available In Nexus? | Yes | https://nexus.onap.org/content/repositories/releases/org/onap/aaf/authz/ | ||
| Are the Java and Docker manifest updated with the same version as in Nexus Release repository? | ??? | AAF "version.properties" files are correct. I understood the "Manifest" files are deprecated, and to only use OOM declarations. | ||
| OOM to Tag Release + Version in Helm Chart | Must be done by OOM | OOM is in charge of Tagging in their Repo until El Alto, when AAF portion moves to our repos. | ||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? It should include at least 1 CSIT that will be run on Lab-xxx-OOM-Daily Jenkins Job | Yes | https://jenkins.onap.org/view/CSIT/ | Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs |
| Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/aaf/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | |
| Has the project passed the Integration Sanity Tests | Yes | No Issues with AAF reported by Integration Team since RC0. SMS had an expired cert, which has been replaced, and it is back in service. | Integration sanity tests in Dublin Release cover:
No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1 No Integration Blocking Issue with no workaround: Dublin Release Integration Test Blocking Issues | |
Has the project done the integration testing with related dependent projects? | Yes | AAF depends on no projects. Other Projects have been working integration, and, other than APPC which needed to replace Cert, no issues. | ||
| Documentation | Has your team completed (reviewed, submitted and cherry picked) all documentation planned for the Dublin Release?
| WIP (2 cherry picks remaining) | https://onap.readthedocs.io/en/dublin/submodules/aai/aai-common.git/docs/release-notes.html | JIRA Query project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC |