Release Checklist

1. Write release notes in NEWS
2. Run tito tag --use-version=x.y.z, where
   x = x + 1; y = 0; z = 0 for major releases (significant changes/new features, backwards compatibility is essentially broken)
   y = y + 1; z = 0 for minor releases (backwards-compatible changes/features)
   z = z + 1 for bug-fix releases (no changes besides bug fixes)
3. Run git push <remote> to push the file changes
4. Run git push <remote> <new-version> to push the new version tag
   • A new tag being pushed triggers a GitHub Actions workflow, resulting in a new release being created
     • A new release being created triggers a Packit-as-a-Service job, resulting in pull requests being created in dist-git for all active branches - review and merge them
5. Build packages for Fedora:
   $ packit build --dist-git-branch=fedora-all
   • If there’s need to build in a side tag, then packit build also accepts --koji-target; pass the tag name you get from e.g. fedpkg request-side-tag --base-tag=f32-build (the base tag will vary for each Fedora version)
6. Create an update in Bodhi:
   $ packit create-update --dist-git-branch=fedora-all … (pass other arguments as needed, e.g. --update-notes and --update-type)