Doc/technotes/release_process.txt

Title: The Thuban Release Process
Author: Thuban development team
Last-Modified: $Date$
Version: $Revision$

How to Release a New Thuban Version

    - Test Thuban until you are sure it works under the following
      reference platforms:

      Debian GNU/Linux 3.0 (plus wxWindows/wxPython 2.4)
      W2000

      All test cases should pass on all platforms.

    - Adjust revision number in setup.py and Thuban/version.py.  See the
      comments in version.py for details.

    - Update thuban.pot and the various .po and .mo files:

      cd po/
      make pot
      make update-po
      make mo

      See po/README for details

    - Update MANIFEST.in

      This is only necessary if the set of files distributed has changed
      in such a way that the old MANIFEST.in doesn't fit anymore. This
      could be e.g. the addition of a new top-level directory such as
      Extensions

    - Produce Source-Archives Thuban-N.N.N.tar.gz and Thuban-N.N.N.zip
 
        python setup.py sdist

    - Build a binary for W2000: Thuban-N.N.N-1.exe

      On a Windows system with Inno Setup installed, unpack the source
      archive (usually the zip file) and run:

        python setup.py bdist_inno

      Test the resulting setup program.

    - Build RPMs for RedHat 7.2

      Take the source tarball and, on a RedHat 7.2 system, run:

        python setup.py bdist_rpm

      Install the rpm and test Thuban. Make sure to have removed any
      other Thuban rpms beforehand.

    - Produce Sample-Data-Tarballs

        python setup.py data_dist

    - Tag the tested sources for CVS:

        cvs tag THUBAN_N_N_N

    - Place packages on ftp server at ftp://intevation.de/thuban/

    - Update http://thuban.intevation.org/download.html accordingly

    - Update/Extend http://thuban.intevation.org/screenshots.html
      if there have been interesting changes/extensions to the UI.

    - Make sure you closed all open bugs that were solved with this
      release.

    - Write announcement including all major improvements

    - Send announcement to following mailing lists:
      [email protected]
      [email protected]

    - Have a beer and thank all contributors :-)


1	bh	2093	Title: The Thuban Release Process
2			Author: Thuban development team
3			Last-Modified: $Date$
4			Version: $Revision$
5
6			How to Release a New Thuban Version
7
8			- Test Thuban until you are sure it works under the following
9			reference platforms:
10
11			Debian GNU/Linux 3.0 (plus wxWindows/wxPython 2.4)
12			W2000
13
14			All test cases should pass on all platforms.
15
16			- Adjust revision number in setup.py and Thuban/version.py. See the
17			comments in version.py for details.
18
19			- Update thuban.pot and the various .po and .mo files:
20
21			cd po/
22			make pot
23			make update-po
24			make mo
25
26			See po/README for details
27
28			- Update MANIFEST.in
29
30			This is only necessary if the set of files distributed has changed
31			in such a way that the old MANIFEST.in doesn't fit anymore. This
32			could be e.g. the addition of a new top-level directory such as
33			Extensions
34
35			- Produce Source-Archives Thuban-N.N.N.tar.gz and Thuban-N.N.N.zip
36
37			python setup.py sdist
38
39			- Build a binary for W2000: Thuban-N.N.N-1.exe
40
41			On a Windows system with Inno Setup installed, unpack the source
42			archive (usually the zip file) and run:
43
44			python setup.py bdist_inno
45
46			Test the resulting setup program.
47
48			- Build RPMs for RedHat 7.2
49
50			Take the source tarball and, on a RedHat 7.2 system, run:
51
52			python setup.py bdist_rpm
53
54			Install the rpm and test Thuban. Make sure to have removed any
55			other Thuban rpms beforehand.
56
57			- Produce Sample-Data-Tarballs
58
59			python setup.py data_dist
60
61			- Tag the tested sources for CVS:
62
63			cvs tag THUBAN_N_N_N
64
65			- Place packages on ftp server at ftp://intevation.de/thuban/
66
67			- Update http://thuban.intevation.org/download.html accordingly
68
69			- Update/Extend http://thuban.intevation.org/screenshots.html
70			if there have been interesting changes/extensions to the UI.
71
72			- Make sure you closed all open bugs that were solved with this
73			release.
74
75			- Write announcement including all major improvements
76
77			- Send announcement to following mailing lists:
78			[email protected]
79			[email protected]
80
81			- Have a beer and thank all contributors :-)
82
83
84
Name	Value
svn:eol-style	native
svn:keywords	Author Date Id Revision