Difference between revisions of "Projects/PIM/Akonadi/Release Howto"

< Projects‎ | PIM‎ | Akonadi
Jump to: navigation, search
m (Text replace - "<code bash>" to "<syntaxhighlight lang="bash">")
m (Text replace - "</code>" to "</syntaxhighlight>")
Line 8: Line 8:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
git log vx.y.(z-1)..
 
git log vx.y.(z-1)..
</code>
+
</syntaxhighlight>
  
 
Finally, update the version number in the top-level CMakeLists.txt and Mainpage.dox and commit/push all your changes.
 
Finally, update the version number in the top-level CMakeLists.txt and Mainpage.dox and commit/push all your changes.
Line 21: Line 21:
 
git push
 
git push
 
git push --tags
 
git push --tags
</code>
+
</syntaxhighlight>
  
 
For a stable release, that is a release from a stable branch, the command looks like this:
 
For a stable release, that is a release from a stable branch, the command looks like this:
Line 30: Line 30:
 
git push
 
git push
 
git push --tags
 
git push --tags
</code>
+
</syntaxhighlight>
  
 
=== Creating a new stable branch ===
 
=== Creating a new stable branch ===
Line 40: Line 40:
 
# do modifications as described above
 
# do modifications as described above
 
git push origin x.y
 
git push origin x.y
</code>
+
</syntaxhighlight>
  
 
Afterwards perform the following steps:
 
Afterwards perform the following steps:
Line 51: Line 51:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
git archive --format=tar --prefix=akonadi-x.y.z/ vx.y.z | bzip2 -9  > akonadi-x.y.z.tar.bz2
 
git archive --format=tar --prefix=akonadi-x.y.z/ vx.y.z | bzip2 -9  > akonadi-x.y.z.tar.bz2
</code>
+
</syntaxhighlight>
  
 
== Step 4: Upload ==
 
== Step 4: Upload ==

Revision as of 21:57, 29 June 2011

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

First, update the NEWS file. It should contain a high-level summary of the changes since the last release. To obtain the full log of all changes since the last release, run the following command or have a look in gitk:

git log vx.y.(z-1)..

Finally, update the version number in the top-level CMakeLists.txt and Mainpage.dox and commit/push all your changes.

Step 2: Tagging/Branching

Tagging a major (pre-)release, i.e. a release from master is done with the following commands:

git checkout master
git tag vx.y.z
git push
git push --tags

For a stable release, that is a release from a stable branch, the command looks like this:

git checkout x.y
git tag vx.y.z
git push
git push --tags

Creating a new stable branch

A new stable branch is created by the following command:

git checkout -b x.y 
# do modifications as described above
git push origin x.y

Afterwards perform the following steps:

  • increment the version number in master

Step 3: Tarball Creation

Run the following command to create the tarball:

git archive --format=tar --prefix=akonadi-x.y.z/ vx.y.z | bzip2 -9  > akonadi-x.y.z.tar.bz2

Step 4: Upload

Upload the tarball somewhere and notify Tom or Volker to move it to http://download.akonadi-project.org/ (unless you are one of those two, then upload directly).

Step 5: Bugzilla

Log into http://bugs.kde.org/, chose Edit Products -> Akonadi -> Add version and add the version you just released.

Step 6: Announcements

Update channel topic on #akonadi.

TODO

Step 7: Dirk

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