Release Process

From Vision
Revision as of 10:27, 22 April 2010 by Anw (talk | contribs) (Created page with '==Release Creation== Files are created in P:\RDT\Vision\_Installers\Releases In Progress. All ASP files are put into the main folder, all files from sub-folders placed in an ide...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Release Creation

Files are created in P:\RDT\Vision\_Installers\Releases In Progress.

All ASP files are put into the main folder, all files from sub-folders placed in an identically-named subfolder.

When all files are pulled together, release notes are created to the current standard - see previous releases for details. These are placed in a Releases sub-folder.

Zip up all the files and sub-folders, and call the patch:

  • Vision_UP<YYMMDD>(_<Site>).zip

FTP the release to Jupiter using the shortcut provided.

Email the distribution list with details of the release, including the release notes.

Release Installation

Note: Ensure that the client has been informed of the release in progress and confirmed that this can go ahead.

Fetch the patch from Jupiter using the provided shortcut in the Releases sub-directory.

Unzip the patch into a sub-folder of the same name.

Move into that folder and copy the entire contents. Note: Make a backup of the files being updated at this stage.

Move to the Vision root directory and paste the contents of the release, choosing to overwrite files or folders where necessary.

Move to the Releases folder. If there is a database upgrade file (named after the patch, with extension SQL), then install this.

To install database upgrade files, start MySQL Query Browser.

Choose 'Load Script' from the file menu.

Load the upgrade SQL file.

Choose 'Continue' from the toolbar - this will install the changes.

Exit the query browser.

Inform the client that the release has been completed.