| 1 |
Section 0: A few days in advance |
| 2 |
|
| 3 |
* Check that release date doesn't clash with KDE's schedule |
| 4 |
* Notify translators and update http://techbase.kde.org/Schedules/Extragear |
| 5 |
-------------------------------------------------------------------------------- |
| 6 |
|
| 7 |
SECTION 1: Preparation |
| 8 |
|
| 9 |
* Check the README file is still relevant |
| 10 |
* Run the "fixuifiles" script from the source-root |
| 11 |
* Run the "bump_plugin_version.rb" script from the folder amarok/ |
| 12 |
* Commit the source to SVN |
| 13 |
-------------------------------------------------------------------------------- |
| 14 |
|
| 15 |
SECTION 2: Creating and Testing the Tarball |
| 16 |
|
| 17 |
* Run the release.rb script; OR |
| 18 |
Follow the guide lines in appendix A |
| 19 |
* Test the following: |
| 20 |
|
| 21 |
$ ./configure && make |
| 22 |
$ ./configure --enable-final --disable-debug && make |
| 23 |
|
| 24 |
* Check it works OK without any amarok files in ~/.kde |
| 25 |
-------------------------------------------------------------------------------- |
| 26 |
|
| 27 |
SECTION 3: Once Happy with the Tarball |
| 28 |
|
| 29 |
* SFtp the tarball to ftpamarok@ktown.kde.org/stable/amarok/VERSION/src or |
| 30 |
ftpamarok@ktown.kde.org/unstable/amarok/VERSION/src |
| 31 |
(If you don't have access, mail sysadmin@kde.org) |
| 32 |
* Notify packagers |
| 33 |
* Write release notes and dot story (and notify KDE-press list if necessary) |
| 34 |
* Add new version to Bugzilla |
| 35 |
-------------------------------------------------------------------------------- |
| 36 |
|
| 37 |
Section 4: The Release Day |
| 38 |
|
| 39 |
* Update download page on the wiki |
| 40 |
* Update the amarok.kde.org front-page |
| 41 |
* Send a witty, intelligent and diligently crafted email to the following lists: |
| 42 |
To: kde-announce-apps@kde.org, amarok@kde.org |
| 43 |
CC: amarok-promo@kde.org |
| 44 |
BCC: kde-extra-gear@kde.org, kde-multimedia@kde.org, |
| 45 |
amarok-packagers@googlegroups.com, (kde-press-announce@kde.org) |
| 46 |
* Blog, update IRC channel topics, ... |
| 47 |
* Update kde-apps.org |
| 48 |
-------------------------------------------------------------------------------- |
| 49 |
|
| 50 |
SECTION 5: After the Release |
| 51 |
|
| 52 |
If you must change anything about the tarball you need to email binner@kde.org |
| 53 |
because otherwise he gets annoyed that the md5 has changed. |
| 54 |
Generally it is not wise to change the tarball, it could annoy the entire |
| 55 |
open-source world! |
| 56 |
-------------------------------------------------------------------------------- |
| 57 |
|
| 58 |
APPENDIX A |
| 59 |
|
| 60 |
This is what the release_amarok script does: |
| 61 |
|
| 62 |
1. Checkout a fresh copy of amarok, its docs and po; cd into the root |
| 63 |
2. Update APP_VERSION in amarok/src/amarok.h |
| 64 |
3. $ `find -name .svn -exec rm {} \;` |
| 65 |
4. $ export WANT_AUTOMAKE=1.6 |
| 66 |
5. $ make -f Makefile.cvs |
| 67 |
6. $ rm -rf autom4te.cache config.h config.log |
| 68 |
7. $ pushd amarok; mv README TODO INSTALL ChangeLog AUTHORS COPYING amarok.lsm ..; popd |
| 69 |
8. $ mv ../multimedia ../amarok-VERSION |
| 70 |
9. $ tar cjf ../amarok-VERSION.tar.bz2 ../amarok-VERSION |
| 71 |
|
| 72 |
APPENDIX B |
| 73 |
|
| 74 |
To create a changelog in html format for updating the various articles and websites, run generate_changelog.rb. It will output a file called ChangeLog.html. |
