Projects/PIM/Akonadi/Release Howto

< Projects‎ | PIM‎ | Akonadi
Revision as of 10:09, 1 December 2009 by Vkrause (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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.

Contents

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):

sh makechangelog

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:

svn cp $SVNPROTOCOL://$SVNUSER@svn.kde.org/home/kde/trunk/kdesupport/akonadi $SVNPROTOCOL://$SVNUSER@svn.kde.org/home/kde/tags/akonadi/x.y.z

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:

svn cp $SVNPROTOCOL://$SVNUSER@svn.kde.org/home/kde/branches/akonadi/x.y $SVNPROTOCOL://$SVNUSER@svn.kde.org/home/kde/tags/akonadi/x.y.z

Creating a new stable branch

TODO

Step 3: Tarball Creation

TODO

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 ;-)


KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal