Release Checklist

1. Make sure there are no regressions (easy for me to say, what with there not being any proper tests)
   • Whatever tests exist must be passing
   • Pylint warnings may be ignored if they only pertain to code style
   • Distribution package builds must not be failing
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> and git push <remote> <new-version>
4. Publish a new release for the tag in https://github.com/abrt/retrace-server/releases/new
5. Packit-as-a-Service should create a PR in dist-git (https://src.fedoraproject.org/rpms/retrace-server) for all active branches, review and merge them
6. Build packages for Fedora and EPEL (note that this command requires Kerberos authentication):
   $ packit build --dist-git-branch epel8,f33,f34,main (update branch names as needed)
7. Create an update in Bodhi:
   $ packit create-update --dist-git-branch epel8,f33,f34 … (update branch names and pass other arguments as needed, e.g. --update-notes and --update-type)
8. Write a short overview in https://github.com/abrt/abrt.github.io/