1
1
Notice to make release tarballs from SVN
2
2
----------------------------------------
4
0/ If the tarball will be created from trunk, check/merge/copy from
5
the stable the files: release_*, NEWS and Changelog.
4
7
1/ Update the release info in these files and commit it to svn :
6
9
- digikam/digikam.lsm - update date as well
11
14
- addPo (for example addPo = ["showfoto"] if showofoto is include in digikam tarball).
13
Note : docs must be set to 'no' because the documentation must be packaged in a separate tarball to decrease the source code tarball size. There is a seperate script to generate this.
15
3/ Commit changed files to svn.
17
4/ Backup old ChangeLog file to ChangeLog.old.
19
5/ Create a fresh ChangeLog file using svn2cl script. Just run it from main digiKam root directory. Please check if ChangeLog file is updated properly.
21
svn2cl can be dowloaded at this url: http://ch.tudelft.nl/~arthur/svn2cl/
22
Just copying this tarball content on digikam root directory to use it.
24
Note : svn2cl need xstlproc program. Please install it before.
26
6/ Copy last changes of fresh ChangeLog file to ChangeLog.old using a simple text editor. Place a release tag at the top of ChangeLog.
28
7/ Renamed ChangeLog.old to ChangeLog and commit it on svn.
30
8/ Run release_digikam.rb script and the releas_digikam_docs.rb
16
Note: docs must be set to 'no' release_digikam.rb because the documentation must
17
be packaged in a separate tarball to decrease the source code tarball size.
18
There is the seperate script release_digikam_docs.rb to generate this.
20
3/ Update ChangeLog with entries since last release:
21
- in existing ChangeLog for the most recent entry
22
- release_digikam_cl.sh and modify 'startfrom' and the svn account
23
- the script and add the generated ChangeLog.new-entries to
24
the ChangeLog file (check for overlap/duplicates)
25
- a release tag at the top of ChangeLog as for the other releases
26
- the ChangeLog.new-entries
28
4/ Look at new ChangeLog entries and add highlights to NEWS file
29
(this can be used for the release announcement too)
32
add a recipe/script that converts CCBUGS: <bug#> from ChangeLog.new-entries
33
to #<bugno>: title of the bug. It needs a check if bug is still closed
34
otherwise reopened bugs are reported as fixed.
36
5/ Commit changed files to svn.
38
8/ Run release_digikam.rb script and the release_digikam_docs.rb
32
40
9/ When tarball is created, decompress it in a temp folder and try to compile it to prevent any problems.
34
10/ Upload tarball to digikam3rdparty.free.fr area via ftp and post a message on digikam-devel@kde.org mailing list to have a feedback from pakagers before posting an offical release annoucement.
42
10/ Upload tarball to digikam3rdparty.free.fr area via ftp and post a message on digikam-devel@kde.org mailing list to have a feedback from packagers before posting an offical release annoucement.
36
44
11/ When official tarball is ready to post, don't forget to copy current trunk svn branch to tags branch (http://websvn.kde.org/tags/digikam/)
added
removed
digikam/PACKAGING
