| Practice Area | Checkpoint | Yes/No | Evidences | How to? | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product Management | Are all tasks associated with the release been marked as "Closed" in Jira? | Yes* | There are tasks pending full closure (marked delivered) related to accessing AAF in OOM, which is working, but not fully code released 10-11. Partly for "night before" fix, partly because Gerrit Repos are unstable. | Use 10-11 to finish full code release activities, now we have AAF OOM candidate | ||||||||||||
| Have all findings from previous milestones been addressed?N/A | Yes | (Note: in RC0, there were still troubles starting and health-checking in OOM. These have been resolved) | ||||||||||||||
| Development | Have all Defects of priority Highest and High been in status "Closed" in Jira? | Yes* |
Owing to 11th hour OOM success, Clients have not been able to assess their OOM access Tickets. These are in "Delivered" state, but await client Closure | |||||||||||||
| Are all JIRA issues used as a reference in a commit in status "Closed" in Jira? | Yes |
| Very 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. | No | |||||||||||||||
| Are all the Jenkins jobs successfully passed (verify + merge jobs)? | All but CSITYes | https://jenkins.onap.org/view/aaf/ CSIT problem is identified by Sai and Gary Wu as being related to "exec with -it". We expect that to be resolved 10-11 Resolve CSIT questions10-24- CSIT jobs working fine until this morning, will re-run | ||||||||||||||
Has the team delivered all their release artifacts in Nexus Release repo? There should be at least ONE version of each artifacts available in Nexus Release repo. | Yes* | https://nexus.onap.org/#nexus-search;gav~org.onap.aaf.authz~~2.1.2~~However, with last minute OOM changes, we will need to release 2.1.2.15~~ | Refer to Independent Versioning and Release Process for procedure | |||||||||||||
| Integration and Testing | Have all CSIT Use Cases (created by each project team) passed? | WIPYes | https://jenkins.onap.org/view/aaf/. 10/24 CSIT Burped this morning, with no changes posted. Investigating | |||||||||||||
| At RC1At RC0, has the Pair Wise testing table been filled out? | Yes | Casablanca Pair Wise Testing master page | ||||||||||||||
| At RC0RC1, have all OOM Release Healtcheck related to your project passed? | WIPYES! | https://jenkins.onap.org/view/External%20Labs/ We will release 2.1.2.1 as part of last minute OOM Success | ||||||||||||||
| At RC0At RC1, is there a Docker image in Nexus Docker-Release repo available for each repository? | Yes | https://nexus3.onap.org/service/rest/repository/browse/docker.release/v2/onap/aaf/ 2.1.3 5 version released on 10/12/2018 | ||||||||||||||
| 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 OOM deployment passed? | WIPYes | httpshttp://jenkinsonapci.onap.org/viewgrafana/External%20Labs/Changes to AAF and OOM are successful as lf 10/10 in non-ONAP lab. Awaits push into ONAP.d/8cGRqBOmz/daily-summary?panelId=8&fullscreen&orgId=1 | ||||||||||||||
Has the Heat deployment passed? (not a gating item for Casablanca) | Yes | https://jenkins.onap.org/view/External%20Labs/ | ||||||||||||||
| Documentation | For RC0RC1, for project delivering binaries, has the team populated and validated all the sections of either the Platform Component or SDK template? | Yes | https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/index.html https://onap.readthedocs.io/en/latest/submodules/aaf/authz.git/docs/sections/release-notes.html https://onap.readthedocs.io/en/latest/submodules/aaf/sms.git/docs/index.html | 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? | Yes | |||||||||||||||
For RC2, for project delivering binaries, has the team populated and validated all the sections of the Release Notestemplate? | ||||||||||||||||
| For RC2, has the Documentation Team provided the final approval for your project documentation? |
Page History
Overview
Content Tools