Release process

This guide sums up steps to perform an upstream release of any of our projects.

Automated

Create (or reopen) an issue titled with "New {major,minor,patch} release". Pick the correct release type. Wait for release-bot to pick the issue up and create a release PR.
Polish the changelog.
Set correct version inside a RPM spec file if there is one. (rpmdev-bumpspec is really helpful here)
Once the PR is approved, merge it. Release-bot will then take care of creating a GitHub release and a corresponding git tag.

Release-bot will handle this.

Packit should/will handle this.

When automation fails, you can always perform any of the automated steps manually.

Create new pull request. Add a changelog entry for the new release. Don't forget to bump the RPM spec file.
Wait for review. Once approved, merge the PR.

Hop into terminal:

$ git checkout master
$ git pull
$ git tag <TAG_NAME>
$ git push --tags

Navigate to the release you just created and paste the changelog entry to the GitHub release description.

Go into terminal and check out the release you just did:
```
$ git checkout 0.8.0
```

Prepare PyPI tarballs

$ rm -rf dist && python3 ./setup.py sdist && python3 ./setup.py bdist_wheel

Upload the tarballs (ask someone on the team to give you permissions to upload tarballs):
```
$ twine upload dist/*
```
Make sure the new release can be fetched from pypi:
```
$ pip3 install packitos==0.8.0
```

Get Fedora Kerberos TGT:
```
$ kinit [email protected]
```
Prepare spec file updates for dist-git:
```
$ packit propose-update --dist-git-branch fedora-all . 0.8.0
```
Once the PRs are approved, merge them.

Build it:

$ packit build --dist-git-branch fedora-all

Create bodhi-updates (fedora-rawhide updates are created automatically):
```
$ packit create-update --dist-git-branch fedora-stable
```