blob: 1688200704a02c6d19a7afa920834e89c4c44743 [file] [log] [blame]
Christian Eglieddc4662009-03-09 13:27:20 +00001-*- outline -*-
2
3This file attempts to describe the maintainer-specific notes to follow
4when hacking liblouis.
5
6* Release Procedure
7These steps describe what a maintainer does to make a release; they
8are not needed for ordinary patch submission.
9
10** Set the version number
11Update the version number in NEWS (with version, date, and release
12type), ChangeLog and configure.ac.
13
14** Commit and tag
15Commit the changes and tag this version
16
17 svn cp https://liblouis.googlecode.com/svn/trunk \
18 https://liblouis.googlecode.com/svn/tags/liblouis_1_3_8
19
20If you know the exact version number that needs to be tagged use
21
22 svn cp https://liblouis.googlecode.com/svn/trunk \
23 https://liblouis.googlecode.com/svn/tags/liblouis_1_3_8 -r 109
24
25** Make the release
26Check out a clean copy in a different directory, like /tmp. Run
27autogen.sh and configure with no special prefixes. Run make distcheck.
28This will make sure that all needed files are present, and do a
29general sanity check. Run make dist. This will produce a tarball.
30
31 ./autogen.sh && configure && make && make distcheck && make dist
32
33** Upload
34Upload tarball to Google project page, tag as "featured". This will
35put the link on the main project page. Remove "featured" tag from
36previous tarball release.
37
38** Announce
39Send an announcement to the liblouis list
40liblouis-liblouisxml@freelists.org. See ANNOUNCEMENT for an example.
41
42** Other web updates
43Update the Google project page. Add the current NEWS to the front
44page.
45
46Also update the page on freshmeat (http://freshmeat.net/projects/liblouis/).
47
48