26
26
ChangeLog is hard work. Therefore a committer should send details of their
27
27
commit. Maybe we sould prepare a better way.
29
3. Checkout a fresh version from svn.
31
svn co svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/trunk
33
4. Do a build test with make releasetest
29
3. Update subpackage versions in make-dist.sh.
31
SSCM_URL="${TAGS_REPOSITORY}/sigscheme-0.7.2"
32
LIBGCROOTS_URL="${TAGS_REPOSITORY}/libgcroots-0.1.3"
34
And set appropriate $RELEASE_SUFFIX.
36
RELEASE_SUFFIX="-alpha"
37
RELEASE_SUFFIX="-beta"
40
4. Export a fresh tree from svn.
42
svn export http://uim.googlecode.com/svn/trunk
46
gosh -I. test/run-test.scm
48
6. Do a build test with make-dist.sh
35
50
This test is not enough, but worth doing. It is especially useful when a
36
51
new file is added. As a TODO, we should do unit testing at this point.
40
This item needs many many description... I must fill this item later.
42
6. Increment the version number in configure.ac and Project-Id-Version in
43
po/*.po, then commit it.
47
8. Copy the source tarball to http://uim.freedesktop.org/releases
53
7. Increment the version numbers in:
57
- Project-Id-Version in po/*.po
59
And increment libtool-version.mk too if ABI is updated.
61
8. Update NEWS and RELNOTE
49
63
9. Tag to tags/uim-x.y.z
51
svn copy svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/trunk\
52
svn+ssh://freedesktop.org/srv/uim.freedesktop.org/svn/tags/uim-x.y.z
54
10. Send a message to uim@freedesktop.org.
56
11. Update the web page.
65
On an alpha release, branch the tree at first.
67
svn cp https://uim.googlecode.com/svn/trunk \
68
https://uim.googlecode.com/svn/branches/x.y
72
svn cp https://uim.googlecode.com/svn/branches/x.y \
73
https://uim.googlecode.com/svn/tags/uim-x.y.z-alpha
75
10. Export the fresh tagged tree from svn.
77
svn export http://uim.googlecode.com/svn/tags/uim-x.y.z-alpha
79
11. Make the distribution.
84
Release suffixes such as '-alpha' and '-beta' is automatically appended.
86
12. Copy the source tarball to the download site.
88
Upload the file by the official uploading script:
90
http://code.google.com/p/support/wiki/ScriptedUploads
92
Don't forget adding appropriate tags as follows.
96
googlecode-upload.py -u yamakenz -p uim \
97
-s 'uim 1.5.0' -l 'Stable,Featured' \
100
Alpha or beta release:
102
googlecode-upload.py -u yamakenz -p uim \
103
-s 'uim 1.5.0-alpha' -l 'Unstable' \
104
uim-1.5.0-alpha.tar.bz2
108
googlecode-upload.py -u yamakenz -p uim \
109
-s 'uim trunk-snapshot20070703' -l 'Snapshot' \
110
uim-trunk-snapshot20070703.tar.bz2
112
And untag 'Featured' from previous final release files by the web
115
13. Update the web pages.
117
http://code.google.com/p/uim/
118
http://code.google.com/p/uim/wiki/FrontPage
120
Update FrontPage first and copy it into the project description
124
The checksums of the files must not directly be written into the
125
anyone-rewritable wikipage, to prevent spoofings. It should be a link to the
126
release announce which contain the checksum information.
129
14. Send a message to uim-en@googlegroups.com
131
<write announcement here>
133
http://code.google.com/p/uim/downloads/
135
MD5 (uim-1.4.0-example.tar.gz) = cff14a6ad95a6a1303b527a86d27bff4
136
MD5 (uim-1.4.0-example.tar.bz2) = b2e96af101a0c51df697990f6311f6f2
137
SHA1 (uim-1.4.0-example.tar.gz) = 3f152c4aa77a3a44d9f74800a8b9d8d3b6c16771
138
SHA1 (uim-1.4.0-example.tar.bz2) = c870c3e8585ce8e4200fe3247021802d922781c6
140
<append RELNOTE here>
142
15. Update Freshmeat entry
144
http://freshmeat.net/projects/uim-inputmethod/