Code Freeze for CPaaS
We want to make sure this happens around 1 week before our projected release date is
Need permissions to be able to approve your MR, otherwise ask ossm-release channel
In 3 product.yml files you will need to change the development_stage from “development” to “code-freeze” this will ensure that no new MR’s are brought into the release.
Example of previous code-freeze
https://gitlab.cee.redhat.com/cpaas-products/openshift-servicemesh/-/merge_requests/112/diffs
Code Freeze for Maistra
We want to make sure this happens around 1 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/tags
https://github.com/maistra/istio-operator/tags
https://github.com/maistra/proxy/tags
https://github.com/maistra/ratelimit/tags
https://github.com/maistra/istio-must-gather/tags
https://github.com/maistra/envoy/tags
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