< PIM | Akonadi Revision as of 20:57, 29 June 2011 (view source)Neverendingo (talk | contribs)m (Text replace - "</code>" to "</syntaxhighlight>")← Older edit Revision as of 16:02, 12 September 2011 (view source) Vkrause (talk | contribs) (Update upload section to the new process using KDE infrastructure rather than Tom's server.)Newer edit → Line 55: Line 55: == Step 4: Upload == == 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).+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: + +* SHA-1 and SHA-256 sums for the files uploaded so we can verify the files. +* Intended destination for the files uploaded (stable/akonadi/src/). == Step 5: Bugzilla == == Step 5: Bugzilla == Revision as of 16:02, 12 September 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 1 Step 1: Changelog, NEWS, version number 2 Step 2: Tagging/Branching 2.1 Creating a new stable branch 3 Step 3: Tarball Creation 4 Step 4: Upload 5 Step 5: Bugzilla 6 Step 6: Announcements 7 Step 7: Dirk 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 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: SHA-1 and SHA-256 sums for the files uploaded so we can verify the files. Intended destination for the files uploaded (stable/akonadi/src/). 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 ;-) Retrieved from "https://community.kde.org/index.php?title=PIM/Akonadi/Release_Howto&oldid=53733" Categories: AkonadiPIM Content is available under Creative Commons License SA 4.0 unless otherwise noted.