At some particular time, we need to create a release branch that will point to the code that will be released. We create a release branch from the development branch. Thanks to that, the development for the next patch version can continue in the devel branch and the current release is not affected.

Tasks:

• If the code freeze belongs to new minor version 3.x, ask Konflux repo admin to set branch ossm-3.x as default one and remove renovate.json file of previous OSSM version.
• Create release branches across all midstream repositories:
  • Sail operator
    • Create a new release branch `release-3.y.z` from the devel branch `release-3.y` according to the OSSM version
  • Istio
    • If this release contains a newer Istio version, create a new release branch according to Istio version `release-1.y.z` from the devel branch `release-1.y`
    • If the Istio version is not changed, the release branch will already be created. In that case,
      • when there aren't any new changes from the previous release, use the same release branch 
      • when there are new changes from the previous release, create new one with prefix, e.g. release-1.24.6-2
  • proxy
    • If this release contains a newer Istio version, create a new release branch according to Istio version `release-1.y.z` from the devel branch `release-1.y`
    • If the Istio version is not changed, the release branch will already be created. In that case
      • when there aren't any new changes from the previous release, use the same release branch 
      • when there are new changes from the previous release, create new one with prefix, e.g. release-1.24.6-2
  • ztunnel
    • If this release contains a newer Istio version, create a new release branch according to Istio version `release-1.y.z` from the devel branch `release-1.y`
    • If the Istio version is not changed, the release branch will already be created. In that case
      • when there aren't any new changes from the previous release, use the same release branch 
      • when there are new changes from the previous release, create new one with prefix, e.g. release-1.24.6-2
  • must-gather
    • Create a new release branch `release-3.y.z` from the devel branch `release-3.y` according to the OSSM version
• When the release branches are created, update konflux gitmodules to use release branches instead of development branches in all branches ( ossm-3.0, ossm-3.1 ... )
• After code freeze, ask someone with Jira Admin privileges to do `Create new versions in Jira` subtask in this JIRA (see Sub-Tasks section)