creating information solutions to your business problems

Release Process

If you are releasing a new version

  • choose a version name/number for the release. This will be of the form N.NN if it is a production release, or of the form UTNNN for user testing.

Branch Preparation

Production branches are copied to a new branch before release, so bug fixes can be made specifically to released versions.

  • Select the appropriate branch to cut the release from. If this is a new production version, then it should be branched from the appropriate source: either the previous production version, or trunk, depending on which branches contain the changes you wish to release.
  • Create the branch 
svn copy http://svn.isotoma.com/svn/loopo/[source] \
         http://svn.isotoma.com/svn/loopo/release_v.vv \
      -m "Creating branch foo"
  • Check the branch out

User Test branches do NOT require their own branch, since these are not in production bugfixes are never made for these releases specifically.

Versioning

  • Open the project in VisualStudio.
  • Select RCOGMMSv2Setup in the Solution Explorer
  • Select the ProductCode Property, and generate a new UUID
  • Open the form MMSv2Forms\System\frmSplash.vb
  • Select the version number in the form, and change the text property, also change the text field with the date underneath.

Releasing the Release

  • The release MUST be built on a machine with an Office 2000 installation. ALso check that the references in MMSv2Forms to Office, Word, Excel and Outlook are pointing to the Office 9 DLLs. If this is not the case, office functionality will crash horribly when run on a machine with Office 2000, although it will work with Office XP or Office 2003.
  • Choose the Release version, and choose to Rebuild Solution
  • Connect to the RCOG VPN
  • Open RCOGNT2\RCOGShared\Projects\MMS\Loopo and create a folder named after the release
  • In this folder create a folder called Install, and copy the release files into it. The release files should be the three installer files, and the AppMeta.xml file.
  • If this is a production release, also copy the AppMeta.xml file to the production location of RCOGNT2\rcogshared\MMSv2 Templates\Metadata. For test releases an alternative location will have been agreed that is referenced in the test database.