GMAT 2013b Release Process

GMAT 2013b Release Process

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

Table of contents

 

Target Date: August 14, 2013

Tasks

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 () and "(x)" for the cross ()

Task

Who

Status

Internal

Status

Notes

Task

Who

Status

Internal

Status

Notes

Review Previous Build Release R2013a Process Notes

All

 

 

Get updated legal statement/license

SPH

N/A

N/A

Needed by Code Freeze.

Update sample scripts

SPH

Needed by App Freeze.

  • Write examples that demonstrate new functionality

  • Clean up all errors and warnings

  • Remove deprecated fields

Write draft Release Notes

JJKP

Needed by App Freeze.

See Writing Release Notes

Update standard descriptive text

SPH

N/A

N/A

Needed by App Freeze.

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

 

Update info on public-facing websites

JJKP

N/A

N/A

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 contacts

SPH

N/A

Needed by Release Day. Located here.

Put in order for additional icons

SPH

(if necessary)

Needed by Visual Freeze.

Configuration audits

 

 

 

PCA and FCA. New for Release 2015 based on NPR stuff.

For QA Complete (August 1)

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 () and "(x)" for the cross ()

Task

Who

Status

Notes

Task

Who

Status

Notes

Verify that all known bugs are checked into JIRA

(All)

 

Complete all JIRA verifications

(All)

 

Complete QA wrap-up tasks

DSC, SPH, JJKP, RQ

 

Address all JIRA tickets awaiting feedback

(All)

 

For Visual Freeze (August 1)

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

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

Task

Who

Status

Internal

Status

Notes

Task

Who

Status

Internal

Status

Notes

Update About panel

LOJ

N/A

N/A

 

Update splash screen

TGG

  1. Add new contributors

  2. Remove contributors who did not contribute to this release

  3. Design updates

  4. Update SplashScreen.psd in GmatDevelopment\moredata\graphics\splash

  5. Use GIMP to save a flattened TIF file and overwrite splash screen in GmatDevelopment\application\data\graphics\splash.

Update icons

TGG

If there are any updates, additions, deletions.

Update gmat_startup_file.txt

JJKP

  • Update formatting, comments

  • Switch to release configuration

All new plugins are added.

Switch to release configuration in script test system

JJKP

Use new rundef.R2013bInternal.template.m.

Are we running public config tests for this release? For next time, need to figure out a way to assemble public release without manual intervention.

Complete visual updates

(All)

Fixed all visual issues known before Visual Freeze.

For Code Freeze (August 1) 

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

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

Task

Who

Status

Internal

Status

Notes

Task

Who

Status

Internal

Status

Notes

Update EOP files

WCS

Update eopc04_08.62-now and run smoke tests.

Update files w/ updated legal statement

LOJ

N/A

N/A

 

Update license text

LOJ

N/A

N/A

Update application/License.txt file.

Final bug fixes

(All)

 

For this release: Should we branch the repo here, instead of after release? We need to allow people to continue working on unrelated items while release work is ongoing.

For App Freeze (August 1) 

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 () and "(x)" for the cross ()

Task

Who

Status

Notes

Task

Who

Status

Notes

Update README.txt

JJKP

Update with major release highlights.

Update extras folder

JJKP

Notepad++ syntax coloring file

Update PDF files in docs folder

SPH/DJC

  • Update watermark: "Draft for Release R2013b"

  • Put into application/docs folder, and individual doc source folders

Gather list of compatibility changes since last release

(Feature leads)

  • Deprecated fields

  • Removed & disabled fields

  • Anything a user would need to know to make R2012b 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

JJKP

See the R2013b Compatibility Issues document.

Update screenshots in User Guide

(Feature leads)

JJKP: 

 

Test User Guide instructions & code

(Feature leads)

JJKP:

  • Tutorials

  • Common Tasks

  • script snippets

  • reference page examples

Update Windows installer package

JJKP

 

Update links in GMAT.ini

JJKP

Moved from R2013a Visual Freeze Stage

  • Help links

    • Welcome page links

Update link tests in TestComplete

TR

  • Help buttons

  • Welcome Page links

  • Help menu links

 

Testing of Release Candidate 1 (August 5-9)

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

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

Task

Who

Status

Notes

Task

Who

Status

Notes

Update README.txt

JJKP

 

Build Windows installer

JJKP/TGG

Version string: R2013b-rc#

Bundle Windows zip

JJKP/TGG

Version string: R2013b-rc#

Run TestComplete smoke tests

TR

These are tests on the packaged versions of GMAT: the installer and the zip bundle.

Run TestComplete system test missions

TR

These are tests on the packaged versions of GMAT: the installer and the zip bundle.

Run script test system

JJKP/TGG

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

At a minimum these need to be run individually by hand.  I ran them by adding the folder, and they run so fast I missed some pretty big problems.  Ideally, these should all be in script regression tests.  Many but not all already are regression tested.

Run TestComplete full regression tests

TR

(For final RC only)

Notes

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

Stage Release (August 12)

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 () and "(x)" for the cross ()

 

Task

Who

Status

Notes

Task

Who

Status

Notes

Bundle source code and upload to SourceForge

DJC

N/A

  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 SourceForge

DJC

N/A

  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"