This page lists all tasks that have to be done for a gPodder release.
Automating this is discussed in #293.
make messages on the master branch and commit changes, then notify translators via the
#518 github issue.
If dependencies have been changed or updated, it’s a good time to update them:
tools/mac-osx/release_on_mac.shfor the python deps with versions in
pip installcommands; update them;
tools/win_installersubdirectory of the gPodder repository.
\# ... test if basic usage works with current data ... mv ~/gPodder ~/gPodder.saved \# ... test gPodder (subscribing + downloading) ... rm -rf ~/gPodder mv ~/gPodder.saved ~/gPodder
Test latest Windows and macOS builds in a similar manner.
src/gpodder/\_\_init\_\_.pywith new version number and release date, update translations and manpages in a single command:
make revbump VERSION=x.y.z
git tag -a -m "gPodder x.y.z release" x.y.z git push --follow-tags
The flatpak build files for flathub are in https://github.com/flathub/org.gpodder.gpodder
flatpak-pip-generator -r <path to tools/requirements.txt in gpodder sources>(see flatpak-builder-tools)
flatpak-builder --user --install build-dir org.gpodder.gpodder.json