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.
Not required, but it’s a good time to update dependencies:
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.
make revbump VERSION=x.y.z
git tag -a -m "gPodder x.y.z release" x.y.z git push --follow-tags