File: release_process.txt

package info (click to toggle)
thuban 1.2.2-2
  • links: PTS, VCS
  • area: main
  • in suites: squeeze
  • size: 7,596 kB
  • ctags: 5,301
  • sloc: python: 30,411; ansic: 6,181; xml: 4,127; cpp: 1,595; makefile: 166; sh: 101
file content (98 lines) | stat: -rw-r--r-- 3,029 bytes parent folder | download | duplicates (5)
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
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
Title: The Thuban Release Process
Author: Thuban development team
Last-Modified: $Date: 2008-02-13 23:31:31 +0100 (Wed, 13 Feb 2008) $
Version: $Revision: 2837 $

How to Release a New Thuban Version

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

      Debian GNU/Linux 4.0 (aka Etch) (using wxWindows/wxPython 2.6)
      optional: Debian GNU/Linux Sid,  Windows XP

      All test cases of stable code 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.bz2 and Thuban-N.N.N.zip
 
        python setup.py sdist --force-manifest

      The  option "--force-manifest" is necessary because there might
      be changed filenames matching the patterns in MANIFEST.in 
      and python 2.4.4's distutils will _not_ recreate MANIFEST if it is
      newer in this case by default. The option makes sure that MANIFEST
      will be created of if MANIFEST.in each time.
    
    - Sign Source-Archives
    	
	gpg2 --detach-sign  Thuban-N.N.N.tar.bz2
	gpg2 --detach-sign  Thuban-N.N.N.zip


Old:- 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.

Old:- 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 within SVN:

         svn copy  svn+ssh://youruserid@scm.wald.intevation.org/thuban/trunk/thuban svn+ssh://youruserid@scm.wald.intevation.org/thuban/tags/thuban-N-N-N-release
	 Afterwards, adjust the version numbers in SVN again.


    - Uploaded packages in the Files section on Wald.

	http://wald.intevation.org/frs/?group_id=6

Old:- 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 issues that were solved with this
      release.

    - Write announcement including all major improvements.

Old:    - Send announcement to following mailing lists:
      thuban-announce@intevation.de
      freegis-list@intevation.de

    - Have a beer and thank all contributors :-)