Versions Compared

Version Old Version 8 New Version 9
Changes made by

Thomas G Grubb

Thomas G Grubb

Saved on

Key

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

...

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

 

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

For Visual Freeze (April

...

30)

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

...

TaskWhoStatus

Internal

Status

Notes
Update About panel

LOJ

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

All new plugins are added.

Switch to release configuration in script test system

JJKP(error)(error)

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

For Code Freeze (April

...

30) 

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

...

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.

For App Freeze (

...

May 5) 

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.

...

TaskWhoStatusNotes
Update README.txtJJKP(error)Update with major release highlights.
Update extras folderJJKP(error)Notepad++ syntax coloring file
Update PDF files in docs folderSPH/DJC(error)
  • 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)(error)
  • 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(error)See the R2013b Compatibility Issues document.
Update screenshots in User Guide
(Feature leads)

(error)

JJKP: (error)

 
Test User Guide instructions & code(Feature leads)

(error)

JJKP: (error)

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

JJKP

(error)

Moved from R2013a Visual Freeze Stage

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

 

Testing of Release Candidate 1 (

...

May 5-May

...

9)

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

...

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

Stage Release (May

...

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.  

...

TaskWhoStatusNotes
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)Download, install, and run after uploading.
Upload Windows zip to SourceForgeJJKP(error)Download and run after uploading.
Post README.txt on SourceForgeJJKP(error) 
Post internal & public release files to MESA networkJJKP(error) 

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 backupJJKP(error)

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 (May

...

14)

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

...