Ace:Release Guidlines: Difference between revisions
From Adapt
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
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. | 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= | |||
The binary distribution should include a | |||
Revision as of 21:34, 24 January 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
The binary distribution should include a
