Versions Compared

Old Version 41

changes.mady.by.user Janet Riley Bowker

Saved on

compared with

New Version 42

changes.mady.by.user Cassandra Boell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

HOW TO build and release Thalia

Contents:

  1. Prepration
  2. Code Build and Release
  3. Deploying the Static HTML

PREPARATION 

ARE YOU DOING A RELEASE?
Before deploying anything, confirm that you won't interrupt anyone else's work:

...

  1. Make sure all developers have checked in their code.
  2. For releases, make sure everyone has resolved their fixed bugs so the release notes are accurate.
  3. Make sure you have no uncommitted code hanging around in your local working copy, if that's what you're using for the build. ("svn status")

CODE BUILD AND RELEASE

Thalia code has two pieces: the IME back end, which is a Java .war file, and the .swf front end, which is written in OpenLazlo. The .swf front-end is built into the IME's .war file, although it's actually a distinct build and may be a separate .war file at some point in the future.

...

  • you can create an album
  • you can create a slideshow 

DEPLOYING the STATIC HTML

Html pages are kept in our subversion repository at svn+ssh://svn.mit.edu/zest/thalia/website/. The HTML is divided into Branches and Trunk, like the code, because the help changes with product versions. Make sure to deploy the HTML from the branch relevant to the release of Thalia which has been deployed on the IME server in question.

...