...
- Ensure all commits are using related TOPIC (one topic for one artifact)
- Add "Release Process Step #' to each commit message (first line)
- Example: https://gerrit.onap.org/r/q/topic:%22CPS-728%22
Step | Action | Results | Examples | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Update release notes | Release notes available on https://docs.onap.org/projects/onap-cps/en/latest/release-notes.html | |||||||||||
2 | Update read-the-docs copies of openapi documentation e.g. for CPS-Core:
For DMI-Plugin:
Note 1. Run Note 2. This step can be skipped if there are no OPEN API changes | Latest (amalgamated) openapi.yaml available in read-the-docs | |||||||||||
3 | Go to latest Gerrit merged review of repo and comment 'stage-release' | ||||||||||||
4 | 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) Note. this file should NOT contain 'tag_release=false' | Maven artifacts are published to maven release repository |
| ||||||||||
5 | 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. ???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? TBC Above step is unclear which Sha is to be used maybe id doesn't matter.... Take the latest built image, retag it without the timestamp : e.g. SO release file
| Docker image is published to docker release repository |
| ||||||||||
6 | Prepare the next release by bumping and merging new version numbers:
| Topic CPS-728 | |||||||||||
7 | 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). | Topic CPS-728 |
Manage Release Branch
Prerequisites
...