| 1 |
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 4.0 (aka Etch) (using wxWindows/wxPython 2.6) |
| 12 |
optional: Debian GNU/Linux Sid, Windows XP |
| 13 |
|
| 14 |
All test cases of stable code 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.bz2 and Thuban-N.N.N.zip |
| 36 |
|
| 37 |
python setup.py sdist --force-manifest |
| 38 |
|
| 39 |
The option "--force-manifest" is necessary because there might |
| 40 |
be changed filenames matching the patterns in MANIFEST.in |
| 41 |
and python 2.4.4's distutils will _not_ recreate MANIFEST if it is |
| 42 |
newer in this case by default. The option makes sure that MANIFEST |
| 43 |
will be created of if MANIFEST.in each time. |
| 44 |
|
| 45 |
- Sign Source-Archives |
| 46 |
|
| 47 |
gpg2 --detach-sign Thuban-N.N.N.tar.bz2 |
| 48 |
gpg2 --detach-sign Thuban-N.N.N.zip |
| 49 |
|
| 50 |
|
| 51 |
Old:- Build a binary for W2000: Thuban-N.N.N-1.exe |
| 52 |
|
| 53 |
On a Windows system with Inno Setup installed, unpack the source |
| 54 |
archive (usually the zip file) and run: |
| 55 |
|
| 56 |
python setup.py bdist_inno |
| 57 |
|
| 58 |
Test the resulting setup program. |
| 59 |
|
| 60 |
Old:- Build RPMs for RedHat 7.2 |
| 61 |
|
| 62 |
Take the source tarball and, on a RedHat 7.2 system, run: |
| 63 |
|
| 64 |
python setup.py bdist_rpm |
| 65 |
|
| 66 |
Install the rpm and test Thuban. Make sure to have removed any |
| 67 |
other Thuban rpms beforehand. |
| 68 |
|
| 69 |
- Produce Sample-Data-Tarballs |
| 70 |
|
| 71 |
python setup.py data_dist |
| 72 |
|
| 73 |
- Tag the tested sources within SVN: |
| 74 |
|
| 75 |
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 |
| 76 |
Afterwards, adjust the version numbers in SVN again. |
| 77 |
|
| 78 |
|
| 79 |
- Uploaded packages in the Files section on Wald. |
| 80 |
|
| 81 |
http://wald.intevation.org/frs/?group_id=6 |
| 82 |
|
| 83 |
Old:- Update http://thuban.intevation.org/download.html accordingly |
| 84 |
|
| 85 |
- Update/Extend http://thuban.intevation.org/screenshots.html |
| 86 |
if there have been interesting changes/extensions to the UI. |
| 87 |
|
| 88 |
- Make sure you closed all open issues that were solved with this |
| 89 |
release. |
| 90 |
|
| 91 |
- Write announcement including all major improvements. |
| 92 |
|
| 93 |
Old: - Send announcement to following mailing lists: |
| 94 |
[email protected] |
| 95 |
[email protected] |
| 96 |
|
| 97 |
- Have a beer and thank all contributors :-) |
| 98 |
|
Parent Directory
| 
Revision Log