Skip to content

new_release.md

Latest commit

 

History

History
36 lines (30 loc) · 2.58 KB

new_release.md

File metadata and controls

36 lines (30 loc) · 2.58 KB
name New release
about [Only for maintainers] Create an issue to track release activities
title Tasks for v<release-tag> release cycle

Tasks

Tasks for a new release vX.Y.Z 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.
  • 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.
  • [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.