Ace:Release Guidlines: Difference between revisions
From Adapt
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
=Packaging= | =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. | |||
Revision as of 20:27, 1 February 2011
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
- export a clean copy of the 'svn export https://subversion.umiacs.umd.edu/ace/trunk ace-test'
- 'mvn package' in root, and make sure the build succeeds.
Clean deploy testing
- From your build, deploy the war file in ace-am/target/ace-am-XXX.war
Upgrade testing
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.
