summaryrefslogtreecommitdiff
path: root/src/ReleaseProcedure
blob: f586a6b2f42588f149b135dbcdc7d7d8daa54375 (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
Procedure for making a GF release:

1. Make sure everything the should be in the release has been
   checked in.

2. Go to the src/ dir.

   $ cd src

3. Edit configure.ac to set the right version number 
   (the second argument to the AC_INIT macro).

4. Edit gf.spec to set the version and release numbers 
   (change %define version and %define release).

5. Commit configure.ac and gf.spec:

   $ cvs commit -m 'Updated version numbers.' configure.ac gf.spec

6. Run autoconf to generate configure with the right version number:

   $ autoconf

7. Go back to the root of the tree.

   $ cd ..

8. Tag the release. (X_X should be replaced by the version number, with
   _ instead of ., e.g. 2_0)

   $ cvs tag RELEASE-X_X

9. Build a source package:

   $ cd src
   $ ./configure
   $ make dist

10. Build an x86/linux RPM (should be done on a Mandrake Linux box):

   $ cd src 
   $ ./configure
   $ make rpm

11. Build a generic binary x86/linux (should be done on a Linux box,
    e.g. banded.medic.chalmers.se):

   $ cd src
   $ ./configure --host=i386-pc-linux-gnu
   $ make binary-dist

12. Build a generic binary sparc/solaris package (should be done on a Solaris box,
    e.g. remote1.cs.chalmers.se):

   $ cd src
   $ ./configure --host=sparc-sun-solaris2
   $ make binary-dist

13. Build a Mac OS X package:

    ???

14. Build a Windows package:

    ???

15. Update website.

16. Party!