Preparing CPaaS to update product.yaml and release.yml and creating a new directory under versions.
1. Copy the latest previous version into a new release directory under versions. Eg. https://gitlab.cee.redhat.com/cpaas-products/openshift-secondary-scheduler-operator/-/commit/f0a34aa7dccd5055ed4645198ce09f10592a46f7. E.g. 1.2.0 in this case
1.1 Bump the previous version (1.1 and 1.1.z) to the new one (1.2 and 1.2.0).
1.2 Don’t forget to extend content_stream_tags with the new y-version.
1.3 And to set release.version to the new y-version.
1.4 And to remove advisory_map.yml so a new advisory gets automatically created (later in the workflow). If not removed the CPaaS will try to update an already existing advisory for the previous release.
1.5 For minor version, use the same CDN repo that was already requested. For major version- verify that CDN rpm repo with major version exists.
2. Create a new branch under the midstream repository (from the latest existing y-stream). Eg. osso-1.2-rhel-8.
2.1 Update upstream_sources.yaml to point to the right branch (master/main branch in general unless chosen differently): https://gitlab.cee.redhat.com/workloads-team/openshift-secondary-scheduler-operator/-/commit/c53063d6e6504f5bd33aed67ccd3594d9e6f4eae#7a6a99745326113eec432e5abd61944c08000645_5_4
2.2 Set the right min OCP version for the release: https://gitlab.cee.redhat.com/workloads-team/openshift-secondary-scheduler-operator/-/commit/c53063d6e6504f5bd33aed67ccd3594d9e6f4eae#c01374fb068f4b5262ec12bb99d3a81e4302744b_17_16
3. Rerun pipeline-seed job to regenerate the jobs for the new release. The newly regenerated jobs will trigger poll-upstream-sources jobs for all available branches/releases.
4. Rerun honeybadger job to generate a new products yaml file for the new y-stream release. E.g. https://gitlab.cee.redhat.com/pipeline/products/-/merge_requests/2063
4.1 Don’t forget to make sure all tests over the MR are passed. E.g. https://gitlab.cee.redhat.com/pipeline/hb/-/pipelines/5315790 failed and the new “OSSO 1.2 ASYNC” release was not created under https://errata.devel.redhat.com/release/active_releases

Resources:
https://docs.google.com/document/d/1Y3q5VqBKwF2X5gV-KfcSRSTLnoeUlHHHhpDbEpntzFQ/edit#heading=h.ums8y4xz2t13
Google space to ask questions: CPaaS Users

Responsible: Engineering