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

< Projects‎ | PIM‎ | Akonadi
Jump to: navigation, search
(Update upload section to the new process using KDE infrastructure rather than Tom's server.)
(Update to new sysadmin ticket system.)
(5 intermediate revisions by one user not shown)
Line 18: Line 18:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
git checkout master
 
git checkout master
git tag vx.y.z
+
git tag -a vx.y.z -m "Akonadi x.y.z"
 
git push
 
git push
 
git push --tags
 
git push --tags
Line 27: Line 27:
 
<syntaxhighlight lang="bash">
 
<syntaxhighlight lang="bash">
 
git checkout x.y
 
git checkout x.y
git tag vx.y.z
+
git tag -a vx.y.z -m "Akonadi x.y.z"
 
git push
 
git push
 
git push --tags
 
git push --tags
Line 55: Line 55:
 
== Step 4: Upload ==
 
== Step 4: Upload ==
  
Upload the tarball to ftp://upload.kde.org/incoming/. Afterward, create a KDE Sysadmin bug report at https://bugs.kde.org/enter_sysadmin_request.cgi - including the following:
+
Upload the tarball to ftp://upload.kde.org/incoming/, using e.g. the following command:
  
* SHA-1 and SHA-256 sums for the files uploaded so we can verify the files.
+
<syntaxhighlight lang="bash">
* Intended destination for the files uploaded (stable/akonadi/src/).
+
ftp -u ftp://upload.kde.org/incoming/ akonadi-x.y.z.tar.bz2
 +
</syntaxhighlight>
 +
 
 +
Afterward, create a KDE Sysadmin ticket at https://sysadmin.kde.org/tickets/ (department "download.kde.org") and fill in the following information in the form:
 +
* Name of the tarball: akonadi-x.y.z.tar.bz2
 +
* SHA-256 sums for the tarball
 +
* Intended destination is stable/akonadi/src/.
 +
 
 +
Wait for the request to be processed (you'll get an email notification) and the mirrors to propagate the new file (~2h).
  
 
== Step 5: Bugzilla ==
 
== Step 5: Bugzilla ==
Line 70: Line 78:
 
TODO
 
TODO
  
== Step 7: Dirk ==
+
== Step 7: <s>Dirk</s>Albert ==
  
Finally, apologize to Dirk for being late again with the release ;-)
+
Finally, apologize to <s>Dirk</s>Albert for being late again with the release ;-)
  
 
[[Category:Akonadi]] [[Category:PIM]]
 
[[Category:Akonadi]] [[Category:PIM]]

Revision as of 09:46, 5 May 2013

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 -a vx.y.z -m "Akonadi x.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 -a vx.y.z -m "Akonadi x.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 to ftp://upload.kde.org/incoming/, using e.g. the following command:

ftp -u ftp://upload.kde.org/incoming/ akonadi-x.y.z.tar.bz2

Afterward, create a KDE Sysadmin ticket at https://sysadmin.kde.org/tickets/ (department "download.kde.org") and fill in the following information in the form:

  • Name of the tarball: akonadi-x.y.z.tar.bz2
  • SHA-256 sums for the tarball
  • Intended destination is stable/akonadi/src/.

Wait for the request to be processed (you'll get an email notification) and the mirrors to propagate the new file (~2h).

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

Finally, apologize to DirkAlbert for being late again with the release ;-)


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