Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.






Review Previous Build Release R2015b Process Notes

Obtain Release ApprovalsSPH  Needed by release day.
Get updated legal statement/licenseSPHN/A Needed by Code Freeze.
Update sample scripts

Needed by App Freeze.

  • Write examples that demonstrate new functionality
  • Clean up all errors and warnings
  • Remove deprecated fields
Write draft Release Notes



Needed by App Freeze.

See Writing Release Notes

Update standard descriptive textSPH (tick) (tick)

Needed by App Freeze.

Will be used in User Guide, websites, release announcement.

Update version number in User Guide cover
SPHrequest is in(tick) (tick)

Needed by App Freeze.

Contact Katy Gammage or Mary Hrybyk-Keith to update cover page.

Next time: integrate sejda-console to do this automatically.

Update info on public-facing websitesTGG  

Needed by Release Day.

See the list of sites. Update this list as well, if necessary.

Updated major sites before announcement. Minor ones can be updated a bit later.

Update release announcement contactsSPH  

Needed by Release Day. Located here.

Put in order for additional iconsSPH(tick)(tick)

(if necessary)

Needed by Visual Freeze.



(DJC here)  A better approach going forward would be to merge master into production, and switch the test system to the production branch.  This probably ought to be done right before building RC1.  The dev team would have 2 options then:

  1. Checkout branches based on what they are working on (i.e. checkout production for bug fixes for the release, and their current clone of master – every one is cloning for new work, right? – for ongoing work)
  2. Alternatively, make bug fixes in master and cherry-pick merge changes into production as bugs are fixed

The former is the better approach, IMO, because it ensures that the bug fix is made on the current code base for the release.

For App Freeze (





App Freeze is a freeze on all application bundle files beyond data and code. This includes documentation, sample scripts, stuff in the extras folder, etc.


Update README.txtSPH 




Update with major release highlights.
Update extras folderJJKPSPH (tick) Notepad++ syntax coloring file
Update PDF files in docs folderSPH/DJC

DJC: (tick)

SPH:  (tick)

  • Update watermark: "Draft for Release R2016a"
  • Put into application/docs folder, and individual doc source folders
Gather list of compatibility changes since last releaseSPH (tick)
  • Deprecated fields
  • Removed & disabled fields
  • Anything a user would need to know to make R2016b scripts compatible with this release.
Update Release Notes
SPH (tick) 
Update screenshots in User Guide
(Feature leads)


SPH: (tick)

RQ: (tick)


Test User Guide instructions & code(Feature leads)

RQ: (tick)


SPH:  (tick)

  • Tutorials
  • script snippets
  • reference page examples

SPH:  only tested features that changed for which I was FDE

Update Windows installer packageJJKPTGG  (tick) 
Update links in GMAT.ini


  • Help links
  • Welcome page links
Update link tests in TestCompleteTR (tick)
  • Help buttons
  • Welcome Page links
  • Help menu links

Testing of Release Candidate 1 (






14 )

This will start with the 2014-05-05 daily build. Repeat this phase until tests check out. Steve will make the call.


  • While this cycle is ongoing is a good time to do wiki updates and cleanup.

Stage Release (


Oct 20)

This is a soft release, putting all the files in place and updating information. Then on release day, we only need to send the announcements.  

Use "(/)" for the checkmark ((tick)) and "(x)" for the cross ((error))


At least tag the test system; consider branching also if the burden on the repo is low.  (In SVN, tagging makes a branch, so tagging already creates a branch.
Tag All ReposDJC(tick)At least tag the test system; consider branching also if the burden on the repo is low.  (In SVN, tagging makes a branch, so tagging already creates a branch.)
Bundle source code
DJC* (tick)
  1. Export the trunk code from svn that is used for the release build when that build is started
  2. Wait for a go/nogo call from testing on the build
  3. Archive the following folder trees into a zip file: src, plugins, build
Bundle data
DJC* (tick)
  1. Use the same export as used for the source bundle
  2. Wait for a go/nogo call from testing on the build
  3. Archive the following folder tree into a zip file: application/data
Upload source bundle to SourceForgeSPH (tick)
  1. Move the zip file to SF
  2. Mark as "staged"
  3. Download the upload and check it
Upload data bundle to SourceForgeSPH  (tick)
  1. Move the zip file to SF
  2. Mark as "staged"
  3. Download the upload and check it
Upload Windows installer to SourceForgeSPH  (tick)
Download, install, and run after uploading.
Upload Windows zip files to SourceForgeSPH (tick) Download and run after uploading.
Post README.rst.txt on SourceForgeSPH  (tick)
Update for new release
Upload docs to documentation siteSPH (tick)
  1. Upload using SSH to
  2. Update HTML with new section
  3. Move "latest" pointer to new folder


Fixed "latest download" to point to new exe.SPH(tick) See instructions here:
Post internal & public release files to MESA networkSPH (tick)  

Branch and tag repositories

Upload source to Git repo (tick) 

Upload src

Change new branch to be active branch (what is checked out by default)

Make SourceForge repository backupSPH (tick)

Follow SourceForge's instructions.Perform the

backup on the Linode server and download the resultant .zip file, since the local network blocks rsync.Here is the Rsync command for us:

    rsync -av .

* DJC can only do steps 1-3 here because of contractual constraints

Release Day (



Use "(/)" for the checkmark ((tick)) and "(x)" for the cross ((error))


Make files visible on SourceForge

JJKP (tick)
07/21: Made visible at time of posting, as "soft" release.
Send out release announcementSPH 
  • Mention GSFC in the announcement
  • Don't include large attachments.
Post release announcement on SourceForgeSPH* (tick)
Post release announcement on GMAT BlogJJKP  
Mark as released in JIRASPH (tick)
Migrate code to SourceForge repositoryJJKP Do we migrate to git at the same time?

This needs to be assigned to a different person; DJC cannot post to SF


See Writing Release Notes

Creating an RC

  1. Create the build
    1. Log into gs580w-gmat-t4 as "gsfc580gmatbuild". The credentials are on the network drive, in the Infrastructure folder.
    2. Start Task Scheduler.
    3. [RC1 only] Disable the "GMAT Daily Build" task, so it doesn't run automatically during the RC cycle (this can make things overly confusing).
    4. Manually run the "GMAT Daily Build" task.
  2. Create the bundles
    1. On your local system, navigate to GmatDevelopment\build\install\windows-nsis. Note that you do not need to pull files down from the Git repository; this process will pull files from the remote build and create the packages in your local directory. There's a README.txt file there that explains things.
    2. Open a MinGW, MSYS2, or Cygwin shell in this directory.
    3. Run 'make assemble VERSION="R2015a-rc#"', where "#" is the number of the RC you're creating. This will create two directories in the current directory: gmat-internal and gmat-public.
    4. Run the following commands to add the User Guide cover. This requires sejda-console.

      Code Block
      sejda-console merge -f ../../../doc/help/src/files/images/Cover-UserGuide-A4-Trimmed.pdf gmat-internal/GMAT/docs/help/help-a4.pdf -o gmat-internal/GMAT/docs/help/help-a4-new.pdf -s all:all:
      mv gmat-internal/GMAT/docs/help/help-a4-new.pdf gmat-internal/GMAT/docs/help/help-a4.pdf
      sejda-console merge -f ../../../doc/help/src/files/images/Cover-UserGuide-Letter-Trimmed.pdf gmat-internal/GMAT/docs/help/help-letter.pdf -o gmat-internal/GMAT/docs/help/help-letter-new.pdf -s all:all:
      mv gmat-internal/GMAT/docs/help/help-letter-new.pdf gmat-internal/GMAT/docs/help/help-letter.pdf
      sejda-console merge -f ../../../doc/help/src/files/images/Cover-UserGuide-A4-Trimmed.pdf gmat-public/GMAT/docs/help/help-a4.pdf -o gmat-public/GMAT/docs/help/help-a4-new.pdf -s all:all:
      mv gmat-public/GMAT/docs/help/help-a4-new.pdf gmat-public/GMAT/docs/help/help-a4.pdf
      sejda-console merge -f ../../../doc/help/src/files/images/Cover-UserGuide-Letter-Trimmed.pdf gmat-public/GMAT/docs/help/help-letter.pdf -o gmat-public/GMAT/docs/help/help-letter-new.pdf -s all:all:
      mv gmat-public/GMAT/docs/help/help-letter-new.pdf gmat-public/GMAT/docs/help/help-letter.pdf
    5. Run 'make VERSION="R2015a-rc#"', where "#" is the number of the RC you're creating. This will create four packages in the current directory: A .zip and a .exe file for both the internal and public versions. Note: To create only an internal version, run 'make internal VERSION="R2015a-rc#"'.
    6. Copy the four package files to the network: \\mesa-file\595\GMAT\Builds\windows\VS2013_build_32\R2015a
    7. To clean everything up afterwards, run "make clean".
  3. Run the script test system on the internal installer package. See Running the script test system, below.