Release process

How a tagged Cloudzilla release is cut. Releases are versioned v<major>.<minor>.<patch>, and while the project is in alpha the minor number tracks the roadmap phase.

1. Freeze the branch

Cut a release branch from main once every issue in the milestone is closed. After the freeze, only fixes land on the release branch.

2. Update the changelog

Move the entries under Unreleased into a new dated section, grouped under Added / Changed / Fixed.

3. Tag and build

git tag -a v0.4.0 -m "Cloudzilla v0.4.0"
git push origin v0.4.0
make build

4. Publish

Create the release from the tag on the Releases page, attach the built binary, and paste the changelog section as the release notes.