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

Compare with Current View Page History

« Previous Version 23 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 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.

Get updated legal statementSPH(error)Needed by Code Freeze.
Configure JIRA for releaseJJKP(error)

Proposed use of JIRA to track tasks:

  • Create "releases" for milestones
  • Mark tickets' Fix By by milestone
  • Enter recurring tasks below as subtasks on main release ticket
  • Create release dashboard
Put in materials printing ticketsJJKP(error)
  • Printed documentation
  • Release CDs
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(error)

Needed by App Freeze.

See Writing Release Notes

Update standard descriptive textSPH(error)

Needed by App Freeze.

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

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.


  • Do we want these release tasks to show up in your JIRA lists, or would you rather use a page like this to track them?
    • No, use wiki page
  • What kinds of printed materials do we want? Bound reference guides? Full copies of the User Guide?
    • print these, but after release


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.

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


  • I added this to capture items that need to be done in order for the developers to get ready for Visual Freeze and beyond.

For Visual Freeze (Mar 27)

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?

    • TestComplete can do this.
  • Do we want to test both Internal and Public versions separately? 
    • Run internal fully. Run public at least on last RC. Revisit next week.
    • Run public configuration on TestComplete next week.

For Code Freeze (April 3)

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.
Update files w/ updated legal statementLOJ(error) 
Final bug fixes(All)(error) 


  • Are there any other data files we need to update?
  • I think we can push this back to March 27. For R2012a, Code Freeze and App Freeze were the same date.

For App Freeze (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.

Update README.txtJJKP(error)Update with major release highlights.
Update PDF files in docs folderSPH/DJC(error)
  • GMAT-Architectural-Specification.pdf
  • GMATEstimationSpecification.pdf
  • GMATMathSpec.pdf
Gather list of compatibility changes since last release(Feature leads)(error)
  • Deprecated fields
  • Removed & disabled fields
  • Anything a user would need to know to make R2012a scripts compatible with this release.
Update Release Notes
Update screenshots in User Guide
(Feature leads)(error) 
Test User Guide instructions & code(Feature leads)(error)
  • Tutorials
  • Common Tasks
  • script snippets
  • reference page examples
Update Windows installer packageJJKP(error) 
Send printed material to TIMSJJKP(error) 

Testing of Release Candidate 1 (April 3–12)

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

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

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) 


  • I don't think we have time to run the GUI regression tests on each release candidate. Do we have GUI smoke tests we can use?
    • Run smoke tests, run full tests on final RC.
  • 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.

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) 
Post README.txt on SourceForgeJJKP(error) 
Post internal & public release files to MESA networkJJKP(error) 

Branch and tag repository

Make SourceForge repository backupJJKP(error)Follow SourceForge's instructions.
Send files to TiMS for CDsJJKP(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?
  • Do we need to tag the test system?
    • Tag at minimum.

Release Day (April 16)


Make files visible on SourceForge

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


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?


  • We need a plan for post-release maintenance of R2013a. How do we decide if something's worth making a service release?
    • CCB will make this decision.
  • Who's planning the release party? Is Darrel planning a trip out here anytime soon?
    • Do party when Darrel comes out April.

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
  • No labels