1. email asst@mit.edu about the scheduled down time ahead of time so they will not be alarmed when the nagios service fails on Thalia.
2. check out the release branch
3. make sure that the following lines are in settings.xml in $M2_HOME/conf/settings.xml . Username and password are for the tomcat manager. Ask if you don't have that information. <server>
<id>prodserver1</id>
<username>username</username>
<password>password</password>
</server>
<server>
<id>prodserver2</id>
<username>username</username>
<password>password</password>
</server>
4. Deployment method 1: command line
goto the directory where the pom.xml resides (the top level branch directory) and type:
mvn tomcat:undeploy -Denv=prod1 (this commands undeploys thalia on isda-thalia5)
mvn clean tomcat:deploy -Denv=prod1 (this command does a clean build and deploys it onto isda-thalia5)
mvn tomcat:undeploy -Denv=prod2 (this commands undeploys thalia on isda-thalia8)
mvn clean tomcat:deploy -Denv=prod2 (this command does a clean build and deploys it onto isda-thalia8)
5. Deployment method 2: via the tomcat manager interface
. src/main/webapp/WEB-INF, remove web.xml and rename web.xml.production to web.xml
4. goto src/main/webapp/WEB-INF/classes/alfresco/ and edit the repository.location value in the file
webseriveclient.properties. The production repository.location value should be:
http://mv.ezproxy.com.ezproxyberklee.flo.org/alfresco/api
5. goto the directory where the pom.xml resides (the top level branch directory) and type "mvn clean package" to generate the ROOT.war file
6. deploy the war onto isda-thalia5 and isda-thalia8 under ROOT (undeploy the ROOT first, and then deploy the new war). :
mvn clean package -Denv=prod1 (this will generate a clean production build).
goto http://mv.ezproxy.com.ezproxyberklee.flo.org/manager/html 
;
undeploy the root (context /)
deployed the newly generated war
repeat this process on isda-thalia11
For details about server config issues, see thalia specific server setup.