Warning, /multimedia/amarok/release_scripts/RELEASE_HOWTO is written in an unsupported language. File is not indexed.

0001 Amarok Release process
0002 ----------------------
0003 
0004 Dependencies:
0005 - The Ultimate KDE Extragear Release Script from git@git.kde.org:releaseme.git
0006 
0007 SECTION 0: A week in advance
0008 
0009  * Check that release date doesn't clash with KDE's schedule
0010  * Notify translators and update http://techbase.kde.org/Schedules/Extragear
0011 --------------------------------------------------------------------------------
0012 
0013 SECTION 1: Preparation
0014 
0015  * Check the README file is still relevant
0016  * Run the "fixuifiles" script from kde-dev-scripts from the repository root
0017  * Run the "bump_plugin_version.rb" script from the repository root
0018  * Set AMAROK_VERSION to the release version at shared/Version.h
0019  * Commit the source to git
0020 --------------------------------------------------------------------------------
0021 
0022 SECTION 2: Creating and Testing the Tarball
0023 
0024  * Run the amarok release script from (tarme.rb).
0025    example: ./tarme.rb --version 2.5.90 --origin trunk amarok
0026  * Test the following:
0027 
0028      $ cmake -DCMAKE_INSTALL_PREFIX=`kf5-config --prefix` -DCMAKE_BUILD_TYPE=RelWithDebInfo ./
0029      $ make
0030 
0031  * mkdir ~/.kde-test && export KDEHOME=$HOME/.kde-test
0032  * Check it works OK without any amarok files in $KDEHOME (i.e. new user config)
0033  * Make a backup of $KDEHOME/share/apps/amarok and $KDEHOME/share/config/amarok*
0034    (release_scripts/backup_userdata.sh)
0035  * Check it works with an existing $KDEHOME, including database updates
0036 --------------------------------------------------------------------------------
0037 
0038 SECTION 3: Once Happy with the Tarball
0039 
0040  * Tag the commit: "git tag -s v2.5.90"
0041  * ftp the tarball to ftp://upload.kde.org/incoming and file a sysadmin request to have it
0042    transfered to stable/amarok/$version/src/ or unstable/amarok/$beta-version/src
0043    Instructions at ftp://upload.kde.org/README
0044  * Notify packagers:
0045 To: kde-distro-packagers@kde.org, Patrick von Reth (TheOneRing, Windows) <vonreth@kde.org>
0046 "
0047 Dear packagers
0048 
0049 Here you can find the beta tarball for the upcoming $version release:
0050 http://download.kde.org/download.php?url=unstable/amarok/$beta-version/src/amarok-$beta-version.tar.bz2
0051 
0052 sha256sum: $(sha256sum tarball.tar.bz2)
0053 
0054 We plan to release the final about 3 weeks from now but please make
0055 this available to users via a specialized beta archive for packaging
0056 is possible. We hope to get as much testers for this beta.
0057 
0058 Thanks for packaging.
0059 The Amarok Team
0060 "
0061 
0062  * Write release notes and dot story (and notify KDE-press list if necessary)
0063  * Add new version to Bugzilla
0064 --------------------------------------------------------------------------------
0065 
0066 SECTION 4: The Release Day
0067 
0068  * Make tarball public
0069  * Update download page on the wiki
0070  * Update the amarok.kde.org front-page
0071  * Send a witty, intelligent and diligently crafted email to the following lists:
0072      To:  kde-announce-apps@kde.org, amarok@kde.org
0073      CC:  amarok-promo@kde.org
0074      BCC: kde-multimedia@kde.org, kde-distro-packagers@kde.org,
0075           (kde-press-announce@kde.org)
0076  * Update IRC channel topics
0077  * Update social networks
0078  * Update kde-apps.org
0079  * Add new version to bugzilla, disable unstable version reporting
0080  * Write blog post
0081  * Publish dot story (for major versions)
0082 --------------------------------------------------------------------------------
0083 
0084 SECTION 5: After the Release
0085 
0086  * Update shared/Version.h to 2.6-git (if the release was 2.6.0)
0087  * `git grep -ipn 'string freeze'` - now is the time to add/change strings
0088 
0089  If you must change anything about the tarball you need to email sysadmin@kde.org
0090  because otherwise they gets annoyed that the md5 has changed.
0091  Generally it is not wise to change the tarball, it could annoy the entire
0092  open-source world!
0093 --------------------------------------------------------------------------------
0094 
0095 APPENDIX
0096 
0097 To create a changelog in html format for updating the various articles and websites, run
0098 generate_changelog.rb.  It will output a file called ChangeLog.html.