• We want to make sure this happens around 2 week before our projected release date is

• Instead of changing a few lines in code like CPaaS we will need to create release branches for the versions that are being released. 
• We create release branches for all of the repositories in Github that are going to be used
• https://github.com/maistra/istio
• https://github.com/maistra/istio-operator
• https://github.com/maistra/proxy
• https://github.com/maistra/ratelimit
• https://github.com/maistra/istio-must-gather
• https://github.com/maistra/envoy
• https://github.com/maistra/prometheus 

• Once the branches are created you need to set the upstream sources to the release branches instead of the maistra/version branches
• Examples of this are:
• https://gitlab.cee.redhat.com/istio/cpaas/containers-midstream/-/merge_requests/630/diffs 
• https://gitlab.cee.redhat.com/istio/cpaas/containers-midstream/-/merge_requests/629/diffs 
• https://gitlab.cee.redhat.com/istio/cpaas/containers-midstream/-/merge_requests/628/diffs 

• Make sure the commits are the same as the release branches before making the changes** 
• Make sure team knows about the code freezes 

How to create release branches:

2.4.4

• Remove Prometheus from repo list (NO LONGER USED)
• Go into the script and change the version to the version for the branch you are creating
• Run the script with this command 
• ./release-branches.sh

2.3.8

• Remove Prometheus from repo list
• Go into the script and change the version to the version for the branch you are creating
• Run the script with this command 
• ./release-branches.sh

2.2.11

• Remove Prometheus from repo list
• Go into the script and change the version to the version for the branch you are creating
• Run the script with this command 
• ./release-branches.sh

Prometheus

• • This will only be done for the 2.3.z and 2.2.z release branches 

For prometheus we use 2.1 branch

• Change the BRANCH to maistra-2.1
• Change VERSION to 2.3.8