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

Compare with Current View Page History

« Previous Version 62 Next »




This page is used to track the process and progress of the R2013a release.

Table of contents


Target Date: April 16, 2013


All dates are referenced to 12:00 noon EDT.

For example, a deadline of March 15 should be interpreted as March 15, 12:00 noon EDT.

Early Tasks

These are long-lead early tasks that can be completed before the detailed release cycle.

Use "(/)" for the checkmark ((tick)).

Get updated legal statement/licenseSPH(tick)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 NotesJJKP(tick)

Needed by App Freeze.

See Writing Release Notes

Update standard descriptive textSPH(tick)

Needed by App Freeze.

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

Commet from SPH: See Welcome to GMAT in user guide

Update info on public-facing websitesJJKP(error)

Needed by Release Day.

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

Update release announcement contactsSPH(error)Needed by Release Day.
Put in order for additional iconsSPH(tick)

(if necessary)

Needed by Visual Freeze.

For QA Complete (March 20)

QA complete means that all known bugs are being tracked, all bug fixes are verified and documented, and the release process can begin.

Use "(/)" for the checkmark ((tick)).

Verify that all known bugs are checked into JIRA(All)(tick) 
Complete all JIRA verifications(All)(tick) 
Complete QA wrap-up tasksDSC, SPH, JJKP, RQ(tick)
  • GUI rename/delete
Address all JIRA tickets awaiting feedback(All)(tick) 

For Visual Freeze (Mar 27)

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

Use "(/)" for the checkmark ((tick)).

Update links in GMAT.ini


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

This was delayed because of some last-minute behavior changes, but nothing here was required for Visual Freeze this time.

Update About panel


(tick)Not needed for R2013a
Update splash screenTGG(tick)
  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.

This was delayed until (TBD) to allow the team to vote on the final design at the 3/28 team meeting.

Update iconsSPH(tick)If there are any updates, additions, deletions.
Update gmat_startup_file.txtJJKP(tick)
  • Update formatting, comments
  • Switch to release configuration

Switch to release configuration in script test system


Use new rundef.R2013aInternal.template.m.

Ran public configuration manually on JJKP's machine on 2013-03-27 build. Decided to run manually on RCs only. For next time, need to figure out a way to assemble public release without manual intervention.

Complete visual updates(All)(tick)Fixed all visual issues known before Visual Freeze.

For Code Freeze (April 5) (was April 3)

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

Use "(/)" for the checkmark ((tick)).

Update EOP filesWCS(tick)Update eopc04_08.62-now and run smoke tests.
Update files w/ updated legal statementLOJ(tick) 
Update license textLOJ(tick)Update application/License.txt file.
Final bug fixes(All)(error)Awaiting decision on GMT-3745

For App Freeze (April 5) (was April 3)

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.

Use "(/)" for the checkmark ((tick)).

Update README.txtJJKP(tick)Update with major release highlights.
Update extras folderJJKP(tick)Notepad++ syntax coloring file
Update PDF files in docs folderSPH/DJC(tick)
  • Done (DJC) GMAT-Architectural-Specification.pdf
  • Done (DJC) GMATEstimationSpecification.pdf
  • Done (SPH) GMATMathSpec.pdf 
  • Update watermark: "Draft for Release R2013a"
  • Put into application/docs folder, and individual doc source folders
Gather list of compatibility changes since last release(Feature leads)(tick)
  • Deprecated fields
  • Removed & disabled fields
  • Anything a user would need to know to make R2012a scripts compatible with this release.

For this release, put a generic blanket statement regarding the change from beta status to production status and point to wiki page.

Update Release Notes
Update screenshots in User Guide
(Feature leads)(tick) 
Test User Guide instructions & code(Feature leads)(tick)
  • Tutorials
  • Common Tasks
  • script snippets
  • reference page examples
Update Windows installer packageJJKP(tick) 

Testing of Release Candidate 1 (April 5–12)

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

Use "(/)" for the checkmark ((tick)).

Update README.txtJJKP(error)(For RC2+) Update with any late-breaking notes.

Build Windows installer

JJKP(error)Version string: R2013a-rc#

Bundle Windows zip

JJKP(error)Version string: R2013a-rc#
Run TestComplete smoke 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 systemJJKP(error)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 scriptsSPH(error) 
Run TestComplete full regression testsTGG(error)(For final RC only)


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

Stage Release (April 15)

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)).

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)Download, install, and run after uploading.
Upload Windows zip to SourceForgeJJKP(error)Download and run after uploading.
Post README.txt on SourceForgeJJKP(error) 
Post internal & public release files to MESA networkJJKP(error) 

Branch and tag repositories

DJC(error)At least tag the test system; consider branching also if the burden on the repo is low.
Make SourceForge repository backupJJKP(error)Follow SourceForge's instructions.

Release Day (April 16)

Use "(/)" for the checkmark ((tick)).


Make files visible on SourceForge

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


Use "(/)" for the checkmark ((tick)).

  • Darrel is visiting sometime in April. Let's do something then.
Print materials
  • Printed documentation (reference booklet, full User Guide)
  • Release CDs
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:

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

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

See Writing Release Notes

Running script test system

In the steps below, "#" is the RC number and "<config>" is "internal" or "public".

  1. Install the version being tested.
  2. Update the test system repo.
  3. Run:
    >> diary('..\log\R2013a-rc#-<config>.log')
  4. Run:
    >> preparegmat('C:\Path\To\GMAT')
  5. Copy the appropriate template (autorundef.R2013aInternal.template.m or autorundef.R2013aPublic.template.m) to a new name and fill in the values:
    1. RunDef.Build: "R2013a-rc#-<config>"
    2. RunDef.GmatExe: path to installed GMAT.exe
    3. RunDef.RegressionBuild: last build date if testing RC1, otherwise, "R2013a-rc#-<config>"
  6. Run:
    >> gmattest <name of rundef.m>
  7. Run:
    >> diary('off')
  8. Post results to network using robocopy:
    >robocopy "C:\path\to\output\R2013a-rc#" "\\mesa-file\595\GMAT\TestResults\win7\R2013a-rc#-<config>" /E /MT /LOG:robocopy.txt

Issues for RC2

  • GMT-3745
  • GMT-3794
  • GMT-3795
  • Update scripts for estimation functionality
  • What to do about MATLAB Interface in bundle?
  • Proper covers on the PDF User Guide
  • OrbitView bug
  • Run OrbitView regression tests
  • No labels