Preparation
__ Synch to head revision
__ Do a "dry run" mvn clean package to make sure there are no errors

VistA Side

__ REMDV on VHAISLBLL2 is currently the master VistA account from which the KIDS build is made. 
__ Edit the EMERGENCY DEPARTMENT 1.0 package to be the current date. 
__ Edit the menu text of the option EDPF TRACKING SYSTEM to be the correct version number.  This usually means removing the text "-SNAPSHOT".  The menu text for this option should look something like “EDIS version 1.0-Tnn”, where nn is the T-version number. 
__ D ^%ZTP1 and make sure none of the routine sized exceed the maximum of 10000 bytes.
__ Comment out the getVPR call in EDPCTRL
__ D ^XINDEX on the EMERGENCY DEPARTMENT 1.0 package. 
__ Make sure there are no errors/warnings. 
__ Scan the variables and globals for obvious errors (write to globals we don't own, missing new commands, ^KEVIN globals, etc.). 
__ Scan the called routines for any entry points that we should not be calling. 
__ Transport the build as a host file (I use /home/kmeldrum/EMERDEPT1_0Tnn.KID).  The header comment may be anything like, "EDIS 1.0 Tnn Build".
__ Uncomment the getVPR call in EDPCTRL
__ Log into REMDM on VHAISLBLL2. 
__ Load and install the build that was just transported. 
__ Make sure the installation runs ok
__ In REMDM do a CHECK1^XTSUMBLD on the EMERGENCY DEPARTMENT 1.0 package so that you have a list of checksums for the sites to verify against.
__ REMDM on VHAISLBLL2 is the account from which Ron makes the KIDS build to send to SQA and sites. 
 

Web Application Side

__ Synch to head revision. 
__ Make sure everything compiles in Flex Builder. 
__ Make sure -no- files are checked out (including index.template.html). 
__ Check out all the pom.xml files that are in top level directories under ED. 
__ Change all the version numbers in the pom.xml files from 1.0-Tnn-SNAPSHOT to 1.0-Tnn. 
__ Check out TrackingModelLocator.as. 
__ Change the version number in it to be "1.0-Tnn" (value assigned to the appClientVersion variable). 
__ Check in the files that were just checked out, noting the Changelist number. 
__ Do "mvn clean package" in the tracking-parent directory. 
__ Make sure the build is successful. 
__ Log into the Weblogic DEV domain. 
__ Upload the new ear (edis-tracking-application-1.0-Tnn.ear in tracking-ear/target). 
__ Stop the currently running edis-tracking web application in DEV (click trash). 
__ Deploy the ear that was just uploaded. 
__ Check to make sure it looks like the application is running correctly. 
__ Log into the Weblogic DEMO domain. 
__ Stop the currently running edis-tracking web application in DEMO (click trash). 
__ Deploy the ear that was uploaded earlier. 
__ Check to make sure it looks like everything is running correctly in DEMO. 
  

When Everything Looks OK

__ Send a message to Ron with the following information that looks something like: 
__ Emergency Department 1.0 Tnn is ready to be built in REMDM. 
__ The changelist number is xxxxx.  (This is the changelist from above, when the pom.xml files were submitted.) 
__ Do “mvn deploy” from the tracking-parent directory to put the artifacts into the repository. 
__ Check out the pom.xml files. 
__ Change the instances of 1.0-Tnn to 1.0-Tmm-SNAPSHOT, where mm is the next version number. 
__ Change the version number in TrackingModelLocator.as to be 1.0-Tmm-SNAPSHOT. 
__ Add artifact inclusion XML blocks (new <artifactItem> block) for the 1.0-Tnn SWFs in the tracking-server-main and tracking-server-bigboard POMs. (near the bottom, use previous version as template)
__ Remove artifact inclusion XML blocks for any deprecated or incompatible versions of the SWFs in the POMs above.
__ Submit the files with the updated version numbers.
__ Put the EMERDEPT1_0Tnn.KID file in the tracking-kids directory (I use WinSCP) and submit it.
__ In REMDV, edit the EDPF TRACKING SYSTEM option menu text to be "EDIS version 1.0-Tmm-SNAPSHOT". 
-- Run 'mvn clean package -Pdev' and deploy the 1.0-Tmm-SNAPSHOT version EAR to the edis.dev weblogic server.

-- Whenever sites get a new version, verify that NEXDEV is in sync with them.
