Release Process

.NET

• Check in any outstanding changes.
• Update to make sure you have the latest programs for all projects.
• Update the version numbers in the AssemblyInfo.cs file(s).
  • If releasing the admin client the versions in the four projects (ePOD_AutoExport, ePOD_WebApp, ePOD_WebServices and EPODServer) need not be kept the same.
  • If releasing the pda client the versions in the two projects (ePODClient and ePODClientUpdater) can be different.
• Copy the release template folder

  P:\EPOD\_Installers\Releases In Progress\EPOD_UPYYMMDD_Template

  to create a release directory.
• Rename the release directory replacing YYMMDD with the date the release is being performed.
• Any SQL changes should be placed within the Release folder, in files UPYYYYMMDD MSSQL.SQL and UPYYYYMMDD MYSQL.SQL
• The Full Database creation scripts should also be maintained and created in the Full DB subfolder.
• Enter any required release notes in the UPYYMMDD Release Notes.txt file in the Release directory.
• Zip up the folder to UPYYMMDD.zip and store in Releases folder
• Label all the Sourcesafe projects affected with a label of UPYYMMDD. Set the text to the list of changes from the release notes.

Releasing Web_App

• Use the publish option against the ePOD_WebApp project (right click project and select publish or select publish ePOD_WebApp option in the Build menu).
  • Set the Publish method to File System.
  • Set the Target Location to the Admin folder within the release directory (e.g. P:\EPOD\_Development\_Releases\ePOD Admin V1.32.7\Admin).
• In folder used for the publish delete the web.config file (if present).
• In folder used for the publish go into the WebServices\Calidus_ePOD\PDAUpdates subdirectory and delete the UpdatesInfo.xml file (if present).
• To release copy the contents of the folder used for the publish to the application folder on the target machine, overwriting any existing files. Do not delete any files (the web.config is not released and the contents of the PDAUpdates folder created by a PDA release).

Releasing PDA

• Set the Debug/Rlease drop-down to Release.
• Build the ePODClientInstaller, ePODUpdateInstaller and ePODClientInstallerComplete projects.
  • To build right click the project and select Build.
  • The ePODClientInstaller and ePODUpdateInstaller projects must be built before the ePODClientInstallerComplete
• Copy the three cab files from your local ePOD_AutoExport\bin\Release folder (e.g. C:\Projects\EPOD\ePOD_WebApp\ePOD_AutoExport\bin\Release) to the PDA folder within the release directory (e.g. P:\EPOD\_Development\_Releases\ePOD PDA V1.31.1.9\PDA).
• To release:
  • Copy the three cab files from the release PDA directory to the PDAUpdates directory on the target machine. This direcotry is below the Admin web application directory in the WebServices\Calidus_ePOD subdirectory.
  • In the same PDAUpdates directory update the version numbers in the UpdatesInfo.xml file.

AutoExport/AutoImport

• Using visual studio get the latest version of the AutoExport or AutoImport processes.
• Use the publish option.
• Copy the contents of the build folder typically (Project\Release) to your release folder

• At this point this should be deployed to Dev and Test.

Android

PDA Client

Official releases for Android are through the Google Play market.

Google Play

Once the APK is built:

• Open Google developer site (https://play.google.com/apps/publish/v2/?dev_acc=06502315555851208789) and log in with the provided user and password.
• Choose the CALIDUS ePOD application by clicking on it.
• Click APK on the menu, and Upload New APK.
• Drag the new version of the APK into the provided box.
• When uploaded, click Publish Now.
• Click Store Listing on the menu.
• Add recent changes. This should be extracted from the latest entry in CHANGELOG.txt.
• Click Save and Publish

Note: In the future it may be that each client will have its own version of the application on the market. If that is the case, ensure that the correct version is built and updated.

Hosted File

To host the file properly, this requires IIS to be updated as follows:

• Start IIS Manager on the server
• Find the hosted EPOD web site (or change top-level default)
• Edit MIME Types
• Add a new one, ".apk", type "application/vnd.android.package-archive".

Once the app is built, drop the app file in your_app_folder\webservices\calidus_epod\PDAUpdates\

Update the UpdatesInfo.xml file as follows:

 <EPOD_CLIENT_ANDROID version="2.00.20" url="http://your.url.com/webservices/calidus_epod/PDAUpdates/your.apk" required="N" />

Attributes:

• version - your build version, without any leading or trailing characters
• url - the url of where this installer may be accessed
• required - if this is a critical bug fix, set this to "Y", else "N"

Note: Case is important!

Access to this APK is then through the url: http://your.url.com/webservices/calidus_epod/PDAUpdates/your.apk

Documentation

Note: This section is not intended as a replacement for standard procedures, but instead a reminder of the responsibilities for releasers.

• Once programs have been packaged and released to the customer's test system, the affected Supimix Logs should be updated to reflect this - their status and sub status should be changed, the Patch number should be updated with the patch version and a comment added e.g. "Release to customer test system in patch 123456/version 1.2.3".
• Once programs have been packaged and released to the customer's live system, the affected Supimix Logs should be updated to reflect this - their status and sub status should be changed and a comment added e.g. "Release to customer live system in patch 123456/version 1.2.3". This comment should contain enough detail for a project resource to find the release notes in the release area or source control.

Note: If multiple programs are being updated on the same log, this may result in multiple releases (i.e. a Device Client release and a Server release). As both can't be held in the patch number, the Server release should take precedence and the device client version number referenced in those release notes and in the Supimix comment.