...
- Verify there are no SNAPSHOTs and we are up-to-date with other team's released artifacts. For Casablanca, the CI/CD daily release job does this by automatically failing if a SNAPSHOT is defined in the pom.xml's.
- Send Helpdesk tickets to LF ONAP release engineering specifying the daily release CI/CD Job to officially release Java artifacts and any docker images generated by that release job. Eg. The LF moves from staging to the appropriate release repository.
- Update the Integration team manifest so the community knows which released artifacts are available. Example gerrit review: https://gerrit.onap.org/r/#/c/42709/
- Update the Demo team heat scripts so the automated External Lab Jobs work and the Integration team has the latest artifacts for testing.
- Example gerrit review: https://gerrit.onap.org/r/#/c/42711/
- If the branch has occurred, then we must also ensure the heat points to the correct branch: https://gerrit.onap.org/r/#/c/49869/1
- Update the OOM team K8S Helm Charts. Example gerrit review: https://gerrit.onap.org/r/#/c/42713/
Note: If using maven version or release plugin, also manually check the versions are set correctly in the POMs, these plugins can miss POMs especially if they do not have Java source code in them.
2. For any new changes to be done post-Release. Then the we must update to the next SNAPSHOT version:
...