You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »




This page is used to track the process and progress of the R2013a release. It is a tailored implementation of a general release process, so some steps may not be applicable directly to this release.

Table of contents


Target Date: April 02, 2013


For Visual Freeze (March 15)

Visual Freeze finalizes all graphical changes to the software, so that screenshots, documentation, and TestComplete can be updated.

Update links in GMAT.ini


  • Help links
  • Welcome page links
Update About panel


Update splash screenTGG(error)
  1. Update SplashScreen.psd in GmatDevelopment\moredata\graphics\splash
  2. Use GIMP to save a flattened TIF file and overwrite splash screen in GmatDevelopment\application\data\graphics\splash.
Update gmat_startup_file.txtJJKP(error)
  • Update formatting, comments
  • Switch to release configuration

Switch to release configuration in script test system

JJKP(error)Use new rundef.R2013aInternal.template.m.
Complete visual updates(All)(error) 


  • Is TestComplete set up to test the Help buttons and the Welcome Page links, or do we need to do it manually?

  • Do we want to test both Internal and Public versions separately?

For Code Freeze (March 15)

Code Freeze is a freeze on the software itself before final testing.

Update EOP filesWCS(error)Update eopc04_08.62-now and run smoke tests.
Get updated legal statementSPH(error) 
Update files w/ updated legal statementLOJ(error) 
Final bug fixes(All)(error) 


  • Are there any other data files we need to update?

For App Freeze (March 22)

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 sample scripts
  • Write examples that demonstrate new functionality
  • Clean up all errors and warnings
  • Remove deprecated fields
Update README.txtJJKP(error) 
Update PDF files in docs folderSPH/DJC(error)
  • GMAT-Architectural-Specification.pdf
  • GMATEstimationSpecification.pdf
  • GMATMathSpec.pdf
Write Release Notes
JJKP(error)See Writing Release Notes
Update screenshots in User Guide
Test User Guide instructions & codeEngineers(error)
  • Tutorials
  • Common Tasks
  • script snippets
Update Windows installer packageJJKP(error) 
Send printed material to TIMSJJKP(error) 


For Release Candidate (March 27)

This will start with the 2013-03-27 daily build.


Build Windows installer


Bundle Windows zip

Run TestComplete regression testsTGG(error)These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run TestComplete system test missionsJMB(error)These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run script test systemSJH(error)These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Test all sample scriptsSPH(error) 
Send files to TiMS for CDsJJKP(error) 

Stage Release (April 1)

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.

Bundle source code and upload to SourceForgeDJC(error)
  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
  4. Move the zip file to SF
  5. Mark as "staged"
  6. Download the upload and check it
Bundle data and upload to SourceForgeDJC(error)
  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
  4. Move the zip file to SF
  5. Mark as "staged"
  6. Download the upload and check it
Upload Windows installer to SourceForgeJJKP(error) 
Upload Windows zip to SourceForgeJJKP(error) 
Revise standard descriptive textSPH(error)Used on wiki, external sites, release announcement...
Update info on public-facing websitesJJKP(error)See the list of sites. Update this list as well, if necessary.
Update release announcement contactsSPH(error) 
Post internal & public release files to MESA networkJJKP(error) 


  • Do we want users to be able to build a working GMAT from the source code bundle? I think we need to include more directories than are mentioned above. (e.g. application?)
  • Why do we need a separate data bundle?

Announce Release (April 2)


Make files visible on SourceForge

Send out release announcementSPH(error) 
Post release announcement on SourceForgeSPH(error) 
Post release announcement on GMAT BlogJJKP(error) 



Branch and tag repository

Make SourceForge repository backupJJKP(error)Follow SourceForge's instructions.
Conduct postmortem reviewSPH(error)This includes gathering feedback, holding the postmortem meeting, and documenting the results.
Submit NTR for next releaseSPH(error) 
Spring cleaning?(error)

General cleanup of infrastructure:

    • \\mesa-file\595\GMAT
    • get rid of old SVN branches
    • anything else?


  • We need a plan for post-release maintenance of R2013a. How do we decide if something's worth making a service release?

Notes for postmortem

Please add your notes to the Release R2013a Process Notes document.

Compatibility changes

This is a list of compatibility changes since R2012a that need to be captured in the release notes.

  • Spacecraft.CurrA1MJD parameter is deprecated

  • ImpulsiveBurn.V, ImpulsiveBurn.N, ImpulsiveBurn.B parameters are deprecated

  • non-Earth planet NutationUpdateInterval field is removed

  • restricted setting CoordinateSystem Epoch, Primary, Secondary, XAxis, YAxis, ZAxis fields

  • restricted setting CoordinateSystem Origin field

  • No labels