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. Write release notes in CHANGELOG.md and stage it for commit (git add CHANGELOG.md)
3. 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)
4. Run git push <remote> and git push <remote> <new-version>
5. Publish a new release for the tag in https://github.com/abrt/faf/releases/new
6. Write a short overview in https://github.com/abrt/abrt.github.io/

Copr package builds and container image builds in Quay and Docker Hub should start automatically after pushing the tag.