Releasing Kobo

Upstream release

1. Create a commit updating release notes and version in setup.py.

Example: https://github.com/release-engineering/kobo/commit/597412cd4b843ddc57a50d8ebc88a77660588b3e

2. Tag the commit as kobo-(version) and push the tag; make sure to use an annotated tag (and signed if possible).

3. After a short delay, the new release will automatically appear on PyPI; confirm at https://pypi.org/project/kobo/. (If the release does not appear, check for problems in Travis CI.)

(FIXME: step (3) is broken as of 2022-02, as the repo migrated away from Travis but release workflow has not been ported to actions yet. Releases can be manually uploaded to PyPI using twine.)

Fedora/EPEL release

1. Update dist-git for Fedora, EPEL

Using fedpkg. ssh://pkgs.fedoraproject.org/rpms/kobo

Work in master branch initially.

Use kobo-<version>.tar.gz from pypi.

Example session:

fedpkg new-sources kobo-0.7.0.tar.gz
rpmdev-bumpspec kobo.spec
vim kobo.spec
# set proper Version, Release, changelog
git add -p
git commit
git push -v

Then merge & push to each other branch relevant for release.

2. fedpkg build

For each relevant branch.

for b in f25 f26 f27 master; do git checkout $b && fedpkg build; done

3. Create bodhi updates

If you built for any branches other than master, create updates at https://bodhi.fedoraproject.org/updates/new , one update per target Fedora/EPEL version.