Release_workflow

This page describes the workflow for doing a PostfixAdmin release.

preparations in SVN

• update $version and $min_db_version in functions.inc.php
• update debian/changelog
• update CHANGELOG.TXT (version number and date)
• check if debian/patches/db_credentials can be applied, refresh if necessary
• commit everything to git
• tag the release (git tag postfixadmin-3.1)

packaging

GingerDog:

• create tarball (name: postfixadmin-$version.tar.gz - no underscores please!)
• GPG-sign the tarball (gpg --detach-sign --armor $tarball) - should result in a $tarball.asc
• create deb:

This creates a tarball without debian/ directory and is required to build the .dpkg!

   # Example for 2.3.5 release:
   git checkout <tag/>
   debian/rules prep
   debian/rules build-package

• mail everything to cboltz

cboltz

• create RPM
• also sign the tarball and merge with GingerDog's $tarball.asc
• upload everything to sourceforge

release

• change the default download link on SF to point to the new tarball (on the "files" page, click the "i" icon next to the tarball and add checkmarks for all platforms)
• update version in update-check.php (and deploy it to postfixadmin.sf.net)
• update channel topic in #postfixadmin
• announce the release in the forum, personal blog, ...