GTG release process

Before release:

  1. code passes tests with commands make check

  2. CHANGELOG and GTG/info.py files are up to date
  3. merge translations from branch lp:~gtg-user/gtg/trunk-translations

  4. retest all again

Release tagging

Tag the revision (use bzr tag) with gtg-RELEASE_NUMBER. bzr tags lists all the tags. Update the page with available relases.

Building the tarball

Use sanity scripts to test creating a tarball. They will tell you missing files in the tarball.

make clean
./scripts/tarball_integrity.py
./scripts/build_integrity.py

You can install GTG into an empty folder so you exactly see what will be installed and what will not.

python setup.py install --prefix=./temp_folder

Create a tarball and upload it to Launchpad:

python setup.py sdist

Debian package

  1. Go to GTG Daily recipe

  2. Click on Request build(s)

  3. Select appropriate distributions and change archive into Stable GTG releases

Apps/GTG/ReleaseProcess (last edited 2015-01-06 10:33:38 by OliverPropst)