< PIM | AkonadiRevision as of 18:26, 30 June 2010 by Winterz (talk | contribs) (→Step 3: Tarball Creation: remove the info about patching create_tarball.rb. not needed anymore)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) 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 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 A new stable branch is created by the following command: svn cp $SVNPROTOCOL://[email protected]/home/kde/trunk/kdesupport/akonadi $SVNPROTOCOL://[email protected]/home/kde/branches/akonadi/x.y Afterwards perform the following steps: increment the version number in trunk adapt the SVN url in the makechangelog script in the new branch Step 3: Tarball Creation You need the tarball creation script from kdesdk for that. cd KDE/kdesdk/scripts/createtarball Next, edit config.ini to contain the following for releases from trunk: [akonadi] mainmodule = trunk/kdesupport submodule = akonadi wholeModule = yes version = x.y.z translations= no remove = makechangelog For releases from the branch, config.ini needs to contain the following: [akonadi] mainmodule = branches/akonadi submodule = x.y wholeModule = yes version = x.y.z translations= no remove = makechangelog Then, run the create_tarball script: ./create_tarball.rb -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. TODO: can we simplify this by e.g. using CPack? 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 In case you are releasing a stable version, also consider updating the recommended stable tags for KDE (kdesupport-for-x.y). 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=53716" Categories: AkonadiPIM Content is available under Creative Commons License SA 4.0 unless otherwise noted.