Release Process

From gPodderWiki

This page lists all tasks that have to be done for a gPodder release.

Contents 1 Two weeks before the release 2 Testing and release management in the repository 3 Release notes/website work 4 Release notifications 5 Debian package 6 Maemo package

[edit] Two weeks before the release

• Update translation templates from source (before branching!)
• Announce stabilization period on mailing list (+call for translations)

[edit] Testing and release management in the repository

All tests carried out here should be following the Functional tests instructions.

• Run make messages and then do German translation
• Test if gPodder works for normal and first-time use cases:

   # ... test if basic usage works with current data ...
   bin/gpodder-backup -c my.gpo.tgz
   bin/gpodder-backup -P
   # ... test gPodder (subscribing + downloading) ...
   bin/gpodder-backup -P -x my.gpo.tgz
   rm my.gpo.tgz

• Run automatic sanity checks and unittests:

   make releasetest

• If any dependencies have changed, update README file and state them there
• Update README file and src/gpodder/__init__.py with new version number and release date

• Update data/credits.txt from the Git history

   git log | git shortlog | grep -v '^[ ]' | sort | uniq | sed -e 's/\(.*\) ([^)]*):/\1/g'

• Update translations and manpage:

   make messages
   make manpage

• Make sure manpages have the correct version in their headings:

   man doc/man/gpodder.1
   man doc/man/gpo.1

• Make the release in the repository:

   git status
   git add file1 [...]
   git commit
   git push
   git tag gpodder-x.y.z
   git push --tags

• Remove release branch if necessary:

   git branch -d gpodder-x.y.z

[edit] Release notes/website work

• Re-generate ChangeLog for inclusion into tarball:

   git checkout gpodder-x.y.z
   git log gpodder-a.b.c..gpodder-x.y.z >ChangeLog

• Create the release source tarball:

   make release
   ls -l dist/

• Go to Berlios.de gPodder New Release Upload Page
• Update gPodder website
• Copy release notes from website and post to the Mailing list
• Update FAQs in the Wiki (if answers changed because of the release)
• Add new version to the bug tracker (gPodder product), so users can report bugs against it

[edit] Release notifications

• Update entry on freshmeat.net
• Update entry on podcatchermatrix.org

[edit] Debian package

• Notify Debian packager that a new release is available

[edit] Maemo package

Maemo 5 packaging described:

git checkout maemo-5
git pull origin maemo-5
git merge gpodder-x.y

Other/older stuff:

• Roll new Maemo package (apt-get source gpodder + uupdate)
• Test on developer device (scp + dpkg -i)
• Upload to Extras (Diablo + Fremantle)