...

Task	Who	Status	Notes
Update README.txt	JJKP	RC1:  RC2-RC5: N/A	Next time: this should probably be "Update Release Notes" to add outstanding bugs, etc.
Build Windows installer	JJKP (backup: TGG)	RC1:  RC2:  RC2-2:  RC3:   RC4:  RC5:	Version string: R2015a-rc# Next time: build manager should do this
Bundle Windows zip	JJKP (backup: TGG)	RC1:  RC2:  RC2-2:  RC3:   RC4:  RC5:	Version string: R2015a-rc# Next time: build manager should do this
Run TestComplete smoke tests	TR	RC3:	These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run TestComplete system test missions	TR	RC3:	These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run script test system	JJKP (backup: TGG)	RC1:  RC2:  RC2-2:  RC3:   RC4:  RC5:	Run the internal installer tests on T4 and the public installer tests on Joel's machine. Run .zip bundle tests afterwards on same build to compare.
Test all sample scripts	SPH	RC3:    RC4:	At a minimum these need to be run individually by hand or run in GUI regression system.  Additionally, they must be run on a system that has no other installations of GMAT.  Past experience has shown that missing files, and configuraiton issues are not caught by running on machines used for development.
Run TestComplete full regression tests	TR	RC4RC3:   RC5RC4:	(For final RC only)

...

At least tag the test system

Task	Who	Status	Notes
Bundle source code	DJC*		Export the trunk code from svn that is used for the release build when that build is started Wait for a go/nogo call from testing on the build Archive the following folder trees into a zip file: src, plugins, build
Bundle data	DJC*		Use the same export as used for the source bundle Wait for a go/nogo call from testing on the build Archive the following folder tree into a zip file: application/data
Upload source bundle to SourceForge	SPH		Move the zip file to SF Mark as "staged" Download the upload and check it
Upload data bundle to SourceForge	SPH		Move the zip file to SF Mark as "staged" Download the upload and check it
Upload Windows installer to SourceForge	SPH		Download, install, and run after uploading.
Upload Windows zip to SourceForge	SPH		Download and run after uploading.
Post README.rst.txt on SourceForge	SPH		Update for new release
Upload docs to documentation site	SPH		Upload using SSH to http://gmat.sourceforge.net/docs/ Update HTML with new section Move "latest" pointer to new folder Post internal & public release files to MESA network SEE NOTES IN SECTION BELOW
Fixed "latest download" to point to new exe.	SPH			Branch and tag repositories	DJC			See instructions here: http://stackoverflow.com/questions/6777327/how-to-manually-set-the-default-download-file-in-a-sourceforge-project
Post internal & public release files to MESA network	SPH
Branch and tag repositories	DJC		At least tag the test system; consider branching also if the burden on the repo is low.	Make SourceForge repository backup	SPH		Follow SourceForge  (In SVN, tagging makes a branch, so tagging already creates a branch.)
Make SourceForge repository backup	SPH		Follow SourceForge's instructions. Perform the backup on the Linode server and download the resultant .zip file, since the local network blocks rsync.

...

1. Log into gs580w-gmat-t4 as "gsfc580gmattest". The credentials are on the network drive, in the Infrastructure folder.
2. [RC1 only] Start Task Scheduler and disable the "Run Script Test" task. You'll need to run the RC tests manually.
3. Uninstall all previous versions of GMAT.
4. Install the version being tested.
   1. Check "Enable MATLAB interface".
   2. Leave "Associate file types" unchecked.
5. Update the test system repo (located at C:\Users\gsfc580gmattest\Documents\GmatTest)
6. In MATLAB (64-bit):
   
   1. Run:
      >> cd C:\Users\gsfc580gmattest\Documents\GmatTest\bin
   2. Run (replace # with RC number and <config> with "internal" or "public"):
      >> diary('..\log\R2015a-rc#-<config>.log')
   3. Run (this command copies application files such as SPICE kernels needed for regression tests into the new installation of GMAT):
      >> preparegmat('C:\Path\To\GMAT')
   4. In C:\Users\testuser\Documents\GmatTest\bin, copy the appropriate template (autorundef.R2015aInternal.template.m or autorundef.R2015aPublic.template.m) to a new name (such as autorundef.R2015aRc1Internal.m) and fill in the values:
      
      1. RunDef.Build: "R2015a-rc#-<config>"
      2. RunDef.GmatExe: path to installed GMAT.exe
      3. RunDef.RegressionBuild: last build date if testing RC1 (look in GmatTest\output for latest folder, such as 2013-07-31), otherwise, "R2015a-rc#-<config>"
   5. Run:
      >> gmattest <name of rundef.m> (e.g. autorundef.R2015aRc1Internal.m) 
   6. Wait until run completes (usually 8+ hours)
   7. Run:
      >> diary('off')
7. In a Windows cmd window, post results to network using robocopy:
   >robocopy "C:\Users\gsfc580gmattest\Documents\GmatTest\output\R2015a-rc#-<config>" "\\mesa-file\595\GMAT\TestResults\win7\R2015a-rc#-<config>" /E /MT /LOG:%TEMP%\robocopy.txt

Updating SourceForge HTML docs page

The Sourceforge page for logging in is here:  https://sourceforge.net/p/forge/documentation/SFTP/

I (SPH) used Filezilla and this was pretty straightforward once succesfully logging in:

Hostname is frs.sourceforge.net

UserName: "YOURSOURCEFORGEUSERNAME,gmat"

Password is: YOURSOURCEFORGEPASSWORD

File Updating

1. Add a new folder for the release under the gmat\htdocs\docs folder
2. Update contents of the new release folder with files from new release
3. Update the gmat\htdocs\docs\index.html to include new folder and to point to the new latest folder.

Image Added