Tasks for v0.13.0 release cycle

[lentzi90]

Tasks

Tasks for a new release v0.13.0 of the Cluster API Provider OpenStack.
For details, see RELEASE.md.

• [When bumping X or Y] Create a new release branch called release-X.Y.
• [When bumping X or Y] Add a new entry of new release branch to depandabot.yml.
• [When bumping X or Y] Add a new entry of new release branch to security-scan.yaml.
• [When bumping X or Y] Add a new entry to metadata.yaml
  as described in the CAPI book
  on the release branch prior to release.
• Push tag to the repository.
• Promote the staging image by
  adding the new sha=>tag mapping to images.yaml. Done in CAPO v0.13.0 kubernetes/k8s.io#8494
• Verify that the new draft release looks good and make changes if necessary.
• Verify that the image was promoted sucessfully.
• Publish the release.
  Mark the release as "latest" if it is the most recent minor release.
  E.g. if both v1.1 and v1.2 are supported with patch releases, then only v1.2.z should be marked as "latest".

Post-release tasks

• [When bumping X or Y] Update the periodic jobs.
  Make sure there are periodic jobs for the new release branch, and clean up jobs for branches that are no longer supported. Done in CAPO: Add release-0.13 and remove release-0.10 kubernetes/test-infra#35501
• [When bumping X or Y] Update the clusterctl upgrade tests
  and the e2e config
  to include the new release branch.
  It is also a good idea to update the Cluster API versions we test against and to clean up older versions that we no longer want
  to test. Done in 🌱 E2E: Run clusterctl upgrade from v0.13 #2714

[lentzi90]

All tasks completed. Closing...