Releasing New Core Versions

When a new minor or major version of the core framework is released it needs to be merged with other CTRNet applications and any custom core changes made within those apps.

This example will use the latest ATIM repository although the same procedure can be used for the MDR or other applications using the core.

• Checkout a local working copy (WC) of the current core version used with ATiM.

svn checkout http://ctrnet-svn.cvsdude.com/atim/vendor/current

• Export the latest core version.

svn export http://ctrnet-svn.cvsdude.com/core/trunk/

• Perform a local file copy of the latest core export directly on top of your local WC of the current core version. Answer 'Yes to All' if prompted to overwrite existing files and folders.

Note: Files that are no longer in use and have been removed can be deleted manually if desired.

• Commit the updated core changes to the /atim/vendor/current/ folder.

svn commit -m "Add your commit notes here."

• Tag this new version, using the latest core version number as the tagged folder name

svn copy http://ctrnet-svn.cvsdude.com/atim/vendor/current \
http://ctrnet-svn.cvsdude.com/atim/vendor/vX.X.X -m "Tagging new core release vX.X.X"

• Checkout a local working copy of the latest full ATiM release.

svn checkout http://ctrnet-svn.cvsdude.com/atim/trunk

• Now we need to merge the changes with the new core and the previous version into the ATiM application.

svn merge http://ctrnet-svn.cvsdude.com/atim/vendor/vX.X.X \
http://ctrnet-svn.cvsdude.com/atim/vendor/current/ <Working Copy Path>

• Commit changes to the trunk

svn commit -m "Add your commit notes here."