< PIM | Akonadi Revision as of 09:09, 1 December 2009 (view source)Vkrause (talk | contribs) (Start to document the Akonadi release process.) Revision as of 17:17, 1 December 2009 (view source) Vkrause (talk | contribs) (→Step 3: Tarball Creation)Newer edit → Line 41: Line 41: == Step 3: Tarball Creation == == Step 3: Tarball Creation == −TODO+You need the tarball creation script from ''kdesdk'' for that. + +<code bash> +cd KDE/kdesdk/scripts/createtarball +</code> + +Edit ''config.ini'' to use the right version, in the ''[akonadi]'' section. Then, run the ''create_tarball'' script: + +<code bash> +./create_tarball -u $SVNUSER -a akonadi +</code> + +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 == == Step 4: Upload == Revision as of 17:17, 1 December 2009 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 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://[email protected]/home/kde/trunk/kdesupport/akonadi $SVNPROTOCOL://[email protected]/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://[email protected]/home/kde/branches/akonadi/x.y $SVNPROTOCOL://[email protected]/home/kde/tags/akonadi/x.y.z Creating a new stable branch TODO Step 3: Tarball Creation You need the tarball creation script from kdesdk for that. cd KDE/kdesdk/scripts/createtarball Edit config.ini to use the right version, in the [akonadi] section. Then, run the create_tarball script: ./create_tarball -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 ;-) Retrieved from "https://community.kde.org/index.php?title=PIM/Akonadi/Release_Howto&oldid=53705" Categories: AkonadiPIM Content is available under Creative Commons License SA 4.0 unless otherwise noted.