...
ARE YOU DOING A RELEASE?
Before deploying anything, confirm that you won't interrupt anyone else's work:
- If building on isda-build1, you must be in ~isdasnap/.k5login .
- For all releases, check in on jabber chat thalia-talk .
- For QA releases, also check in with QA testers in thalia-QA .
- For production releases, email asst@mit.edu as well as thalia-ops@mit.edu (preferably with the same message, so both will see any replies) about the scheduled down time ahead of time so they will not be alarmed when the nagios service shows a Thalia failure.
- Write the release notes! They live here. The release notes contain a list of what changed in this release: new features, bug fixes, underlying changes like an Alfresco upgrade, etc. Release notes have three purposes: they give QA specific information about what to test, they remind you what changed in the release long after you've forgotten, and they're the raw material for the email that gets sent to users. If you don't know what changed, it's probably a bad idea to do a release. Include the link to the knownissues page in the release notes.
- Update the knownissues page at svn+ssh://svn.mit.edu/zest/thalia/website/Trunk/help/. Remove resolved issues and add new issues. This page needs to be manually uploaded as part of the release process; see below about Deploying Static HTML.
...
- Java: we use the Java version 1.6 JDK; there are a wide variety of packagings and installation methods if you don't already have it; ask the net about this one. Make sure your JAVA_HOME environment variable is set correctly. (On isda-build1, set JAVA_HOME=/usr/java/jdk1.6.0.)
- Subversion: if "svn --version" results in "command not found", you need subversion. Again, packagings vary; your operating system may be able to get it for you, or download it from http://subversion.tigris.org.
- maven: if "mvn -version" results in "command not found", you need to download the latest version of maven (currently 2.0.7) from http://maven.apache.org/download.html and install it locally, making sure to add maven's bin directory to your path.
- Repository access: if "svn ls svn+ssh://svn.mit.edu/zest/thalia" doesn't do something useful, you can't check out the code; you need to be in the zest-cvs moira group to access the repository.
- For the UI build only: if "lzc --help" doesn't give you useful help information for the OpenLaszlo compiler, you need to install version 4.0.2 from http://www.openlaszlo.org; this is hairy enough that it's been split off into a separate wiki page: OpenLaszlo. If you're on isda-build1, just make sure /home/lps-4.0.2/bin is in your PATH.
- On isdabuild1, isdasnap's maven settings are in ~isdasnap/.m2 . This includes settings.xml, which you'll need for maven deployments.
Log in to isda-build1.mit.edu
Any test, staging, or production build is built as user isdasnap on isda-build1.mit.edu . This ensures we are installing identical executables in all environments. To ssh in, you must be in ~isdasnap 's .k5login file.
Check OUT THE SOURCE CODE
svn checkout svn+ssh://username@svn.mit.edu/zest/thalia
(Note the revision number reported; you'll want it later to confirm the release.)
Front end code is in thalia/ui/trunk ; back end code in thalia/ime/Trunk .
BUILDING THE FRONT END
N.B #1.: These instructions replace the old interactive build using the OpenLaszlo server's dynamic compilation facilities.
...