This allows users to go directly to the action page whenever a release needs to be cut. Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
1.6 KiB
How to do a Kata Containers Release
This document lists the tasks required to create a Kata Release.
Requirements
- GitHub permissions to run workflows.
Release Process
Check GitHub Actions
We make use of GitHub actions in the
minor
and
major
files from the
kata-containers/kata-containers
repository to build and upload release
artifacts.
Those actions are manually triggered and are responsible for generating a new
release (including a new tag), pushing those to the
kata-containers/kata-containers
repository.
Check the actions status page to verify all steps in the actions workflow have completed successfully. On success, a static tarball containing Kata release artifacts will be uploaded to the Release page.
Improve the release notes
Release notes are auto-generated by the GitHub CLI tool used as part of our release workflow. However, some manual tweaking may still be necessary in order to highlight the most important features and bug fixes in a specific release.
With this in mind, please, poke @channel on #kata-dev and people who worked on the release will be able to contribute to that.
Announce the release
Publish in Slack and Kata mailing list that new release is ready.