Ace:Release Guidlines - Revision history

Shake: /* Git Release */

2016-11-28T21:33:06Z

Git Release

@@ Line 24: / Line 24: @@
 # export the source in the tags/ace-xxx version, tar/gz it and upload to redmine
-=Git Release=
+= Releasing with Git and UMObj =
-# mvn versions:set to $RELEASE
-# git add all pom.xml
+===Git Brancing===
-# git commit
+# git checkout -b release-$VERSION
-# git tag -a ace-$RELEASE -m 'ace-$RELEASE'
+# mvn versions:set -DnewVersion=$VERSION-RELEASE
-# git archive --format=tar.gz --prefix=ace/ master > ace-$RELEASE-src.tar.gz
+# check pom.xml
-# mvn versions:set to next snapshot
+# find . -type f -name '*.versionsBackup' -delete
-# git add all pom.xml
+# git commit -a -m 'Bump $VERSION release'
-# git commit
+# mvn package && test war and deployment
-# git push
+# git checkout master

Shake: Add git release instructions

2016-01-14T21:02:00Z

Add git release instructions

← Older revision		Revision as of 21:02, 14 January 2016
Line 23:		Line 23:
	# upload the two new binary versions in ace-dist/target to redmine.		# upload the two new binary versions in ace-dist/target to redmine.
	# export the source in the tags/ace-xxx version, tar/gz it and upload to redmine		# export the source in the tags/ace-xxx version, tar/gz it and upload to redmine

			=Git Release=
			# mvn versions:set to $RELEASE
			# git add all pom.xml
			# git commit
			# git tag -a ace-$RELEASE -m 'ace-$RELEASE'
			# git archive --format=tar.gz --prefix=ace/ master > ace-$RELEASE-src.tar.gz
			# mvn versions:set to next snapshot
			# git add all pom.xml
			# git commit
			# git push

Toaster at 20:40, 1 February 2011

2011-02-01T20:40:24Z

← Older revision		Revision as of 20:40, 1 February 2011
Line 18:		Line 18:
	# Check error log for errors, check display for major feature changes, run test audit on existing colleciton, register new collection.		# Check error log for errors, check display for major feature changes, run test audit on existing colleciton, register new collection.

	=~~Packaging~~=		=Releasing=
	~~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.~~		When you have fully tested everything, use maven to generate the current release and update the current project with the next snapshot.
			# Run mvn release:prepare in the root project
			# upload the two new binary versions in ace-dist/target to redmine.
			# export the source in the tags/ace-xxx version, tar/gz it and upload to redmine

Toaster at 20:29, 1 February 2011

2011-02-01T20:29:20Z

← Older revision		Revision as of 20:29, 1 February 2011
Line 9:		Line 9:

	=Clean deploy testing=		=Clean deploy testing=
			# Create a new database using the current ace ace-am.sql file.
	# From your build, deploy the war file in ace-am/target/ace-am-XXX.war		# From your build, deploy the war file in ace-am/target/ace-am-XXX.war

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

	=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.		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.

Toaster at 20:27, 1 February 2011

2011-02-01T20:27:19Z

← Older revision		Revision as of 20:27, 1 February 2011
Line 14:		Line 14:

	=Packaging=		=Packaging=
	~~The~~ binary distribution ~~should include~~ a		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.

Toaster at 21:34, 24 January 2011

2011-01-24T21:34:26Z

← Older revision		Revision as of 21:34, 24 January 2011
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.

	'Source 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

Toaster at 21:26, 24 January 2011

2011-01-24T21:26:19Z

New page

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.

'Source Testing'