Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Info

Target Date: August 14, 2013

Tasks

Info

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

TaskWhoStatus

Internal

Status

Notes

Review Previous Build Release R2013a Process Notes

All (tick)(tick) 
Get updated legal statement/licenseSPHN/AN/ANeeded by Code Freeze.
Update sample scripts
SPH(error)(tick)

Needed by App Freeze.

  • Write examples that demonstrate new functionality
  • Clean up all errors and warnings
  • Remove deprecated fields
Write draft Release NotesJJKP(tick)(tick)

Needed by App Freeze.

See Writing Release Notes

Update standard descriptive textSPHN/AN/A

Needed by App Freeze.

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

 

Update info on public-facing websitesJJKPN/AN/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 contactsSPH(error)N/A

Needed by Release Day. Located here.

Put in order for additional iconsSPH(tick)(tick)

(if necessary)

Needed by Visual Freeze.

For QA Complete (August 1)

...

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

TaskWhoStatusNotes
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(tick)

 

Address all JIRA tickets awaiting feedback(All)(error) 

For Visual Freeze (August 1)

...

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

TaskWhoStatus

Internal

Status

Notes
Update About panel

LOJ

N/AN/A 
Update splash screenTGG(tick)(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.
Update iconsTGG(tick)(tick)If there are any updates, additions, deletions.
Update gmat_startup_file.txtJJKP(tick)(tick)
  • Update formatting, comments
  • Switch to release configuration

All new plugins are added.

Switch to release configuration in script test system

JJKP(tick)(tick)

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)(error)(tick)Fixed all visual issues known before Visual Freeze.

For Code Freeze (August 1) 

...

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

TaskWhoStatus

Internal

Status

Notes
Update EOP filesWCS(tick)(tick)Update eopc04_08.62-now and run smoke tests.
Update files w/ updated legal statementLOJN/AN/A 
Update license textLOJN/AN/AUpdate application/License.txt file.
Final bug fixes(All)(error)(error) 
Warning

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.

...

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

TaskWhoStatusNotes
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)
  • 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)(tick)
  • 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(tick)See the R2013b Compatibility Issues document.
Update screenshots in User Guide
(Feature leads)

(tick)

JJKP: (tick)

 
Test User Guide instructions & code(Feature leads)

(tick)

JJKP: (tick)

  • Tutorials
  • Common Tasks
  • script snippets
  • reference page examples
Update Windows installer packageJJKP(tick) 
Update links in GMAT.ini

JJKP

(tick)

Moved from R2013a Visual Freeze Stage

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

 

Testing of Release Candidate 1 (August 5-9)

...

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

TaskWhoStatusNotes
Update README.txtJJKP(error) 

Build Windows installer

JJKP/TGG(error)Version string: R2013b-rc#

Bundle Windows zip

JJKP/TGG(error)Version string: R2013b-rc#
Run TestComplete smoke testsTR(tick)These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run TestComplete system test missionsTR(tick)These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run script test systemJJKP/TGG(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)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 testsTR(error)(For final RC only)
Info
titleNotes
  • While this cycle is ongoing is a good time to do wiki updates and cleanup.

...

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

 

TaskWhoStatusNotes
Bundle source code and upload to SourceForgeDJCN/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 SourceForgeDJCN/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"
  6. Download the upload and check it
Upload Windows installer to SourceForgeJJKPN/ADownload, install, and run after uploading.
Upload Windows zip to SourceForgeJJKPN/ADownload and run after uploading.
Post README.txt on SourceForgeJJKPN/A 
Post internal & public release files to MESA networkJJKPN/A 

Branch and tag repositories

JJKP(error)At least tag the test system; consider branching also if the burden on the repo is low.
Make SourceForge repository backupJJKPN/A

Follow SourceForge's instructions.

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

Release Day (August 14)

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

TaskWhoStatusNotes

Make files visible on SourceForge

SPHN/A 
Send out release announcementSPHN/A
  • Mention GSFC in the announcement
  • Don't include large attachments.
Post release announcement on SourceForgeDJCN/A 
Post release announcement on GMAT BlogJJKPN/A 

Post-Release

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

...

  1. Log into gs580w-gmat-t4 as "gs580w-gmat-t4\testuser". The credentials are on the network drive, in the Infrastructure folder.
  2. [RC1 only] Start Task Scheduler and disable the "Run Script Test" task. You'll need to run the RC tests manually.
  3. Install the version being tested.
    1. Check "Enable MATLAB interface".
    2. Leave "Associate file types" unchecked.
  4. Update the test system repo .located in c:\users\testuser\Documents\GmatTest
  5. In MATLAB (64-bit):
    1. cd c:\users\testuser\Documents\GmatTest\bin
    2. Run (replace # with RC number and <config> with internal or public keyword):
      >> diary('..\log\R2013b-rc#-<config>.log')
    3. Run (this command copies application files such as spice kernels needed for regression tests into the new installation of GMAT):
      >> preparegmat('C:\Path\To\GMAT')
    4. Copy the In the c:\users\testuser\Documents\GmatTest\bin, copy the appropriate template (autorundef.R2013bInternal.template.m or autorundef.R2013bPublic.template.m) to a new name (such as autorundef.R2013bInternalRC1.template.m) and fill in the values:
      1. RunDef.Build: "R2013b-rc#-<config>"
      2. RunDef.GmatExe: path to installed GMAT.exe
      3. RunDef.RegressionBuild: last build date if testing RC1 (look in GmatTest\output for latest folder, such as 2013-07-31), otherwise, "R2013b-rc#-<config>"
    5. Run:
      >> gmattest <name of rundef.m> (e.g., autorundef.R2013bInternalRC1.template.m) 
    6. Wait until run completes (usually 8+hours)
    7. Run:
      >> diary('off')
  6. In a Windows cmd window, 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

...