Deployment

Perform the following steps to deploy a SimStadt feature release:

1. Ensure that all projects are up to date, do compile and that all executables work as expected.
2. Adapt eu.simstadt.desktop.SimStadtApp.applicationVersion() and property "simstadt.version" in SimStadt deploy-common.xml
3. Update User Guide
4. Update Release Notes
5. Execute deploy.xml in project SimStadt as Ant script
6. Execute deploy.xml of each workflow providing project (e.g. SimStadtWorkflowsEnergy) as Ant script to add the workflows to the distribution created above
7. Execute deploy.xml of each project that provides web services on top of existing workflows (e.g. MonthlyEnergyBalanceWebService) as Ant script to add the web services to the distribution created above
8. On a Mac, set execution flag for *.command files from terminal: "chmod a+x *.command"
9. Test new release in stand-alone mode!
10. Tag new release in Subversion, e.g.: Copy trunk to tags/release_1.4 (in Eclipse, use Branch/Tag... from context menu over trunk).
11. Distribute new release, e.g. by copying the zipped directory to Redmine, and inform users.

To work on bugfixes based on a certain release, one has to create a bug-fixing branch first, if there is no one yet, e.g.: copy tags/release_1.4 to branches/bugfixes_1.4

To publish a bugfix release, follow the steps above, except of step 7. Instead of tagging the trunk, you tag the bugfixes release like this: copy branches/bugfixes_1.4 to tags/release_1.4.1

Note: Never commit on a tagged version, but only on trunk or a branch!