Get updated legal statement/license

SPH

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

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 websites

JJKP

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

Needed by Release Day. Located here.

Put in order for additional icons

SPH

(if necessary)

Needed by Visual Freeze.

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)

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

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

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)

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

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)

Bundle source code and upload to SourceForge

DJC

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

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

Make SourceForge repository backup

JJKP

Follow SourceForge's instructions.

Perform the backup on the Linode server and download the resultant .zip file, since the local network blocks rsync.

Make files visible on SourceForge

SPH

Send out release announcement