Deployment procedure

1. Ensure all issues with a target milestone of the version you're about to deploy are either closed or bumped to a future milestone.
2. All code should be merged to trunk/head/tip/whatever the DVCS of the moment calls it.
3. Tag the revision you are going to deploy as Aldates-vM-N where M and N are the major and minor version numbers for the deployment.
4. Edit the Release notes page to include a section relevant to the version you are about to deploy.
   • Newer versions should be towards the top of the page.
5. Stop the GUI running on the client.
6. SSH to the controller and stop the running controller daemon: sudo service AldatesXController stop
7. Update the controller's code: git pull -u in /opt/AldatesX

• Note: this is currently a lie, since the controller has a Mercurial checkout instead.

1. Restart the controller daemon: sudo service AldatesXController start
2. Update the client's code: git pull -u in /opt/AldatesX
   • Note: The church user does not have write access to /opt/AldatesX, you'll need to be pi
3. Restart the client interface.
4. E-mail a copy of the relevant release notes to the sound desk, CCing (at least) John T, Steven G and @jamesremuscat.
5. Have a cup of tea.