Difference between revisions of "PIM/Akonadi/Release Howto"
|Line 40:||Line 40:|
Revision as of 13:23, 8 January 2010
How to do a release of the Akonadi server? I ask that myself and then Tom every time I have to do it. So, finally document that here.
Step 1: Changelog, NEWS, version number
Run the makechangelog script in the source directory (which either is trunk or branches/akonadi/<version> depending on if you are doing a major (pre-)release or a minor one):
That will add all revisions since the last time to the ChangeLog file.
Next step is to update the NEWS file, run svn diff ChangeLog and summarize the changes for that.
Finally, update the version number in the top-level CMakeLists.txt and commit all your changes.
Step 2: Tagging/Branching
Tagging a major (pre-)release, i.e. a release from trunk is done with the following (server side and thus fast) svn command:
Obviously, replace protocol, username and version with appropriate values.
For a stable release, that is a release from a stable branch, the command looks like this:
Creating a new stable branch
A new stable branch is created by the following command:
Step 3: Tarball Creation
You need the tarball creation script from kdesdk for that.
Edit config.ini to use the right version, in the [akonadi] section. Then, run the create_tarball script:
./create_tarball.rb -u $SVNUSER -a akonadi
Add a -w there if you are using https instead of ssh to access subversion.
Wait a bit and check the tarball created in the current directory. Should be akonadi-x.y.z.tar.bz2.
Step 4: Upload
Upload the tarball somewhere and notify Tom to move it to http://download.akonadi-project.org/.
Finally, apologize to Dirk for being late again with the release ;-)