blob: ec2ca3ceed69a6c08ffa0fc09ff0d8e07eda34a7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
INSPIRED FROM AMAROK ONE
Section 0: A few days in advance
* Check that release date doesn't clash with KDE's schedule
* Notify translators and update http://techbase.kde.org/Schedules/Extragear
--------------------------------------------------------------------------------
SECTION 1: Preparation
* Check the README file is still relevant
* Bump Version Number (in the CMakeLists.txt file)
* Commit the source to GIT
--------------------------------------------------------------------------------
FIXME SECTION 2: Creating and Testing the Tarball
* Run the "release_script.sh"
VERSION=qualcosina
git tag -s $VERSION
git archive --prefix=rekonq-$VERSION/ $VERSION | bzip2 > releases/rekonq-$VERSION.tar.bz2
* Test the following:
$ ./configure && make
$ ./configure --enable-final --disable-debug && make
* Check it works OK without any rekonq files in ~/.kde
--------------------------------------------------------------------------------
FIXME SECTION 3: Once Happy with the Tarball
* SFtp the tarball to:
- ftpamarok@ktown.kde.org/stable/amarok/VERSION/src
(If you don't have access, mail sysadmin@kde.org)
* Notify packagers
* Write release notes and dot story (and notify KDE-press list if necessary)
* Add new version to Bugzilla
--------------------------------------------------------------------------------
Section 4: The Release Day
* Update download page on the wiki
* Update the rekonq.kde.org front-page
* Send a witty, intelligent and diligently crafted email to the following lists:
- To: kde-announce-apps@kde.org, rekonq@kde.org
- BCC: kde-extra-gear@kde.org, kde-press-announce@kde.org
* Blog, update IRC channel topics, ...
* Update kde-apps.org
--------------------------------------------------------------------------------
|
