Ace:Release Guidlines

The tests should be performed prior to an ACE release. As many of these as possible should be included in the maven/hudson configs for automated testing.

Prior to release testing, please make sure all bugs/features for that version have been completed on Redmine. https://scm.umiacs.umd.edu/redmine/adapt/projects/ace/roadmap. Update maven version and footer version prior to creating a release package.

Source Testing

1. export a clean copy of the 'svn export https://subversion.umiacs.umd.edu/ace/trunk ace-test'
2. 'mvn package' in root, and make sure the build succeeds.

Clean deploy testing

1. Create a new database using the current ace ace-am.sql file.
2. From your build, deploy the war file in ace-am/target/ace-am-XXX.war

Upgrade testing

1. Grab the previous ace release, install the schema and war file
2. register the test collection.
3. shutdown instance, run update sql file, drop in new war file
4. Check error log for errors, check display for major feature changes, run test audit on existing colleciton, register new collection.

Packaging

A binary distribution can be created by running 'mvn package' in the root project. This will create a binary tgz and zip file in ace-dist/target that has all necessary war, db, and documenation.