Chapter 2. Release Management

Whenever the project development team decides to build a new release, it follows the procedure described in Creating a new version. This procedure will mark the required files for that version in the repository.

Additionally, it is necessary to provide an installable versions of KMyMoney2. The following chapters explain how to produce the various files. They all assume that you have checked out a version of the project using a release tag.

2.1. Tar Ball

The first step is to produce a source tar-ball archive. Two possible ways exist to do that

The name for the tar-ball archive is derived from the projects name and the respective version. For this example I use the version 0.4pre2 which leads to a base filename of kmymoney2-0.4pre2.tar with various endings according to the compression used (gzip or bzip2).

2.1.1. KDevelop

If you are used to the KDevelop integrated development environment (IDE) you just select the Project/Make distribution/Source-tgz menu entry which will create the file for you in the projects top directory with an appropriate name (e.g. kmymoney2-0.4pre2.tar.gz)

2.1.2. Shell

If you are using the shell to execute commands, you might execute make dist from the top directory of the project. This leads to the same result, the kmymoney2-0.4pre2.tar.gz file.

2.1.3. Size optimization for tar-ball

The above described methods deliver a GZIPed tar-archive. As BZIP2 gives a better compression ratio, you might want to transform the archive to a BZIP2 compressed version with the following commands.


  thb:~> gunzip kmymoney2-0.4pre2.tar.gz
  thb:~> bzip2 kmymoney2-0.4pre2.tar

This results in a file called kmymoney2-0.4pre2.tar.bz2 which is the final version of the source tar ball.