...
Step | Action | Results | Examples | |||||
---|---|---|---|---|---|---|---|---|
1 | Update release notes | Release notes available on https://docs.onap.org/projects/onap-cps/en/latest/release-notes.html | Change 123658 | |||||
2 | Update read-the-docs copies of openapi documentation e.g. for CPS-Core:
Note. Run | Latest (amalgamated) openapi.yaml available in read-the-docs | ||||||
3 | Go to latest Gerrit merged review of repo and comment 'stage-release' | |||||||
34 | Add and merge 'x.y.z.yaml' file to releases folder of the repository root. It describes the release and refers to maven-stage job previously ran. Note: This step is ignored for CPS Temporal (no Maven artifact delivered) | Maven artifacts are published to maven release repository | ||||||
45 | Add and merge 'x.y.z-container.yaml' file to releases folder of the repository root. It describes the release and refers to maven-docker-stage job previously ran. Set "ref" to the (full) SHA of the git commit to be tagged. Take the latest built image, retag it without the timestamp : e.g. SO release file
| Docker image is published to docker release repository | ||||||
56 | Prepare the next release by bumping and merging new version numbers:
| |||||||
67 | Update https://gerrit.onap.org/r/q/project:oom with the release specific changes:
Before pushing changes to the release-specific OOM branch, it is required to push them to master first. If it can not be done, then specify a reason in the release-specific change (for example, image version number is branch specific and it is expected that it could be different in master branch and release branch). |
...