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

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

GUI rename/delete

Address all JIRA tickets awaiting feedback

(All)

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

Task

Who

Status

Notes

Update links in GMAT.ini

JJKP

Help links

Welcome page links

Is this really a viz freeze issue?

Update link tests in TestComplete

SJH

...

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

LOJ

Not needed for R2013a

Update splash screen

TGG

...

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

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 icons

SPH

If there are any updates, additions, deletions.

Update gmat_startup_file.txt

JJKP

Update formatting, comments

Switch to release configuration

Switch to release configuration in script test system

JJKP

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)

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

Task

Who

Status

Notes

Update EOP files

WCS

...

Update eopc04_08.62-now and run smoke tests.

Update files w/ updated legal statement

LOJ

Update license text

LOJ

Update application/License.txt file.

Final bug fixes

(All)

...

Info

For next release: Consider branching 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 (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 ().

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

...

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)

...

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

JJKP

...

Update screenshots in User Guide

(Feature leads)

...

Test User Guide instructions & code

(Feature leads)

...

Tutorials

Common Tasks

script snippets

reference page examples

Update Windows installer package

JJKP

...

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

Task

Who

Status

Notes

Update README.txt

JJKP

...

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

Build Windows installer

JJKP

...

Version string: R2013a-rc#

Bundle Windows zip

JJKP

...

Version string: R2013a-rc#

Run TestComplete smoke tests

TGG

...

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

Run TestComplete system test missions

JMB

...

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

Run script test system

...

JJKP

...

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

TGG

...

(For final RC only)

Info

title

Notes

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

Task

Who

Status

Notes

Bundle source code and upload to SourceForge

DJC

...

Export the trunk code from svn that is used for the release build when that build is started

Wait for a go/nogo call from testing on the build

Archive the following folder trees into a zip file: src, plugins, build

Move the zip file to SF

Mark as "staged"

Download the upload and check it

Bundle data and upload to SourceForge

DJC

...

Use the same export as used for the source bundle

Wait for a go/nogo call from testing on the build

Archive the following folder tree into a zip file: application/data

Move the zip file to SF

Mark as "staged"

Download the upload and check it

Upload Windows installer to SourceForge

JJKP

...

Download, install, and run after uploading.

Upload Windows zip to SourceForge

JJKP

...

Download and run after uploading.

Post README.txt on SourceForge

JJKP

...

Post internal & public release files to MESA network

JJKP

...

Branch and tag repositories

DJC

...

At least tag the test system; consider branching also if the burden on the repo is low.