Prepare a new release environment

These actions should be done before or just after a major release to create a new major version environment.

• Create a maintenance branch
• Update ITechnicalStrings.TEST_VERSION and ITechnicalStrings.JAJUK_CODENAME constants

Updating development server to keep automatic build working

You need to create the new SVN maintenance branch prior doing these steps.

• Temporary deactivate auto build script

mv /etc/cron.d/auto_detect_svn_change_and_build /

• Edit build script and change version number of SVN_MAINTENANCE_BRANCHE_NAME

vi /svn-jajuk/jajuk_build.conf 
SVN_MAINTENANCE_BRANCHE_NAME="maintenance-1_5"

• Change maintenance SVN build.xml files

Edit branches/maintenance-1_5/src/scripts/build.xml

• • change version:

      <property name='version' value='1.5.1_b1' />

• • change test value to "test":

      <property name='test' value='test' />

• • change WAR name from jajuk-trunk-${test}.war to jajuk-${test}.war

      <echo message=' JNLP war file in:      ${rootdir}/jajuk-${test}.war' />

• • change destination WAR name

      <war destfile='${rootdir}/jajuk-${test}.war' webxml='${srcdir}/packaging/jnlp/web.xml'>

• • Commit changes

• Change trunk SVN build.xml files

Edit trunk/jajuk/src/scripts/build.xml

• • Change: version and test value to "test":

      <property name='version' value='1.6dev_20080209' />
      <property name='test' value='test' />

• • Commit changes

• Re-activate auto build script:

mv /auto_detect_svn_change_and_build /etc/cron.d/

• Wait and see if both trunk and new maintenance packages are properly created.