1. 48 hours before the scheduled release, create a ticket for the application integration team: help.mit.edu, create a ticket for isda-admin. Include the desired date for the release (note that this should be a tuesday or a wednesday), and the path where ops team should expect to find the .war file for the release. This is typically a directory you create on isda-build1 in isdasnap's home directory, using the naming convention sprintXX-release-monthday where month-day should be the month-day of proposed release. Example: /home/isdasnap/sprint6b-release-july1.
2. Look at the release notes, and see if there any special instructions for the release engineer for this release. Any special instructions for a given release should be at the bottom of the release notes.
3. The morning of the release day, ssh to isda-build1.mit.edu.
   • ssh -l isdasnap isda-build1.mit.edu 
4. If you have not already created a directory, do so now (see #1 for naming convention). 
5. cd into that directory, and checkout the ui from the branch to be released
   • svn co svn+ssh://svn.mit.edu/zest/thalia/ui/branches/thalia-UI1.0-sprintXX ./ui
6. Then checkout the ime from the branch to be released
   • svn co svn+ssh://svn.mit.edu/zest/thalia/ime/Branches/thalia1.0-sprintXX ./ime
7. cd into the ui directory, and compile:
   • mvn compile
8. cd into the ime directory, and create the war file:
   • mvn clean package -Denv=prod1 -Dincludeui=true -Duipath=/home/isdasnap/<directory-for-release>/ui
9. cd into the ime/target directory, to be sure ROOT.war has been created.
10. Then check the webserviceclient.properties file in ime/target/ROOT/WEB-INF/classes/alfresco/webserviceclient.properties, and make sure that the alfresco repository is pointing to isda-thalia6
11. Email Hunter, or whoever on the application integration team is doing the release, to confirm location of the war file. 
12. Release is generally done after 6:30 pm. Its a good idea to be available online, in case ops have any questions. It is also a good idea to run some basic tests such as browsing, uploding, downloading to make sure nothing obvious is messed up. Be sure to run those tests against both isda-thalia5 and isda-thalia8.
13. email thalia-dev to notify people that the release is out. QA will run some basic tests the next day and a user email is sent out to confirm to the users that the release has happened. .
14. If the release is done and successful, please tag both the UI and IME build.