[Inteproxy-commits] r245 - trunk

[scm-commit@wald.intevation.org]

Author: bjoern
Date: 2010-03-19 14:31:44 +0100 (Fri, 19 Mar 2010)
New Revision: 245

Modified:
   trunk/HowTo-Release.txt
Log:
Added "HowTo make a new InteProxy Server release".



Modified: trunk/HowTo-Release.txt
===================================================================
--- trunk/HowTo-Release.txt	2010-03-19 13:17:34 UTC (rev 244)
+++ trunk/HowTo-Release.txt	2010-03-19 13:31:44 UTC (rev 245)
@@ -42,3 +42,36 @@
 6. Update versions and URLs on the homepage
 
 7. Announce the new release on the mailing lists.
+
+
+HowTo make a new InteProxy Server release
+=========================================
+
+1. Take care everything is checked in properly.
+   Adjust version numbers in
+   server/doc/conf.py
+   and commit (analog previous releases in ChangeLog)
+
+2. Run
+   $ python2.4 test/runtests.py
+   Only proceed if no failures are reported. Else fix the reported bugs.
+
+3. Create a source archive:
+   $ export INTEPROXYVERSION=SERVER-1.0.0
+   $ cd ..
+   $ svn export https://svn.wald.intevation.org/svn/inteproxy/trunk InteProxy-$INTEPROXYVERSION
+   $ tar -czvf InteProxy-$INTEPROXYVERSION.tar.gz InteProxy-$INTEPROXYVERSION
+
+4. Create PDF-file InteProxyServer.pdf.
+
+5. Create a new release "SERVER-1.0.0" on GForge and upload files InteProxy-SERVER-1.0.0.tar.gz,
+   InteProxyServer.pdf.
+
+5.1 Tag the release in SVN:
+
+   $ export YOUR_USERNAME=name
+   $ svn copy -m "Tagged as realease 'release-$INTEPROXYVERSION'" svn+ssh://$YOUR_USERNAME@svn.wald.intevation.org/inteproxy/trunk svn+ssh://$YOUR_USERNAME@svn.wald.intevation.org/inteproxy/tags/release-$INTEPROXYVERSION
+
+6. Update versions and URLs on the homepage
+
+7. Announce the new release on the mailing lists.