Release Process

From gPodderWiki

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

Contents 1 How long will it take? 2 Two weeks before the release 3 Last changes before release/Testing 4 Release notes/website work 5 Release notifications 6 Debian package 7 Maemo package

[edit] How long will it take?

• The 0.10.4 release process took about two hours.
• The 0.11.0 release process also took about two hours.
• The 0.11.1 release process took a bit less than two hours.
• The 0.11.2 release process took about one hour and 45 minutes.
• In the 0.11.3 release process, we wrote automation scripts.

[edit] Two weeks before the release

• Update translation templates from source (before branching!)
• Copy trunk to branches/gpodder-x.y.z in the repository
• Only commit bug fixes and translation updates to branch
• Announce stabilization period on mailing list (+call for translations)

[edit] Last changes before release/Testing

• Test if gPodder works (also with removed ~/.config/gpodder/ i.e. first-time use case)
• Run make releasetest to check for problems and do automatic sanity checks
• Review ChangeLog to see if any dependencies have changed (update README then)
• Update README file and bin/gpodder with new version number and release date
• Run make messages and make generators for translations and manpage
• Make sure manpage has the correct version in its heading
• Update translations
• make cl, do the release commit (be sure to merge all changes that affect trunk to into it now)
• SVN tag: Do a svn cp of /branches/gpodder-x.y.z to /tags/gpodder-x.y.z
• Remove SVN branch after successful SVN tagging

[edit] Release notes/website work

• Make release tarball: make release (tarball is then in dist/gpodder-version.tar.gz)
• Upload release tarball to ftp.berlios.de
• BerliOS file release system (developer.berlios.de)
• Update Roadmap in Wiki
• Run "scripts/new-release" in the website development tree
• Customize "content/oldnews.html" for release text
• Commit changes to gPodder website (add screenshots); make sync
• Copy release notes from website and post to the Mailing list
• Update FAQs in the Wiki (if answers changed because of the release)

[edit] Release notifications

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

[edit] Debian package

• Roll new Debian package (new dependencies/suggests?; distro is unstable?); mark fixed bugs from Debian BTS
• Send new Debian package to sponsor

[edit] Maemo package

• Roll new Maemo package (new dependencies/suggests?; distro is chinook/diablo?)
• Upload to Maemo Extras (Chinook + Diablo)