summaryrefslogtreecommitdiffstats
path: root/PACKAGING
blob: 4acd87d177ca19bafd07f6671c8c249f1eb8a50e (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
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
How to release kipi & co.
----------------------------------------
1. Release libkipi
2. Release kipi-plugins


1. Release libkipi
 a) Update release info
    libkipi/libkipi.lsm
    libkipi/libkipi/version.h
    libkipi/libkipi.pc.in

    To do that you can use the "prepare_libkipi.rb" script, change the 
    release version ("version" and "version_n" fields) and run it.
    Don't forget to commit your changes :)

 b) Update Changelog
    - to do that use the "release_kipi_changelog.sh" script
      release_kipi_changelog.sh libkipi oldest-revision-or-date new-release-version
    - edit Changelog and modify the wrong lines (if any)
    - Commit your changes

 c) Build the source tarball
    - use the "release_libkipi.rb"
      edit the script and change the "version" field
      if you're releasing an svn snapshot set "usesvnver" to "yes"
      run it and get libkipiXXX.tar.bz2

 d) Uncompress and test the tarball
    - check if all the files are right in
    - check if the file RELEASE.rev is in and with the right revision number
    - check if it builds correctly.

 e) Upload tarball for testing 
    Before an official release upload the tarball for testing used sites are
    digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends 
    on who is releasing :)
    Send a mail to kde-imaging@kde.org and digikam-devel@kde.org to have a 
    feedback from pakagers before posting an offical release annoucement.

  f) Upload tarbal on SF and update kipi site
     official site for uploading the release is http://sourceforge.net/projects/kipi
     web page to be update is http://extragear.kde.org/apps/kipi/
     to update this last you have to get, change and commit it from
     XXX@svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
     Send a mail to announce the official release.

2. Release kipi-plugins
 a) Update release info
    kipi-plugins/kipi-plugins.lsm
    kipi-plugins/common/include/pluginsversion.h

    To do that you can use the "prepare_kipiplugins.rb" script, change the 
    release version ("version" field) and run it.
    Don't forget to commit your changes.

 b) Update Changelog
    - to do that use the "release_kipi_changelog.sh" script
      release_kipi_changelog.sh kipi-plugins oldest-revision-or-date new-release-version
    - edit Changelog and modify the wrong lines (if any)
    - Commit your changes

 c) Build the source tarball
    - use the "release_kipi-plugins.rb"
      edit the script and change the "version" field and check the "addPo" one for po files
      if you're releasing an svn snapshot set "usesvnver" to "yes"
      run it and get kipi-pluginsXXX.tar.bz2

 d) Uncompress and test the tarball
    - check if all the files are right in
    - check if the file RELEASE.rev is in and with the right revision number
    - check if it builds correctly.

 e) Upload tarball for testing 
    Before an official release upload the tarball for testing used sites are
    digikam3rdparty.free.fr or www.linux.it/~anaselli/kipi-plugins - depends 
    on who is releasing :)
    Send a mail to kde-imaging@kde.org and digikam-devel@kde.org to have a 
    feedback from pakagers before posting an offical release annoucement.

  f) Upload tarbal on SF and update kipi site
     official site for uploading the release is http://sourceforge.net/projects/kipi
     web page to be update is http://extragear.kde.org/apps/kipi/
     to update this last you have to get, change and commit it from
     XXX@svn.kde.org/home/kde/trunk/www/areas/extragear/apps/kipi
     Send a mail to announce the official release.