GMAT R2018a Release Process

GMAT R2018a Release Process

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

Release Lead Roles

Role

Assignee

Authority/Responsibility

Role

Assignee

Authority/Responsibility

Release Manager

MES

"owns" release, initiates process, creates tracking page, sends daily status updates, tracks issues to completion, makes sure everyone gets their stuff done, brings decisions to CCB/team, maintains tracking page, collects lessons learned, documents process improvements for next release. Must be reachable and preferably in the office during critical stages like creating and testing RCs.

Build Manager

TDN: Windows

WCS: Mac

DJC: Linux

controls build system, creates RCs, sends RC availability announcements. Must be reachable and preferably in the office during critical stages like creating and testing RCs.

Test Manager

GUI: TR

Script: SPH

control GUI/script testing for each RC.  Must be reachable and preferably in the office during critical stages like creating and testing RCs.

Release Risks

This is a list of all risks (opened and closed) related to smooth release of R2015a.

Owner

Status

Description

Resolution

Owner

Status

Description

Resolution

DSC

Open

Batch Estimator may need inner loop editing for LRO.

Investigating inner loop and a "freeze" criteria similar to GEODYN

 

 

 

 

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

Notes

Task

Who

Status

Notes

Update sample scripts

DSC

Needed by App Freeze.

  • Write examples that demonstrate new functionality

  • Clean up all errors and warnings

  • Remove deprecated fields

Write draft Release Notes

SPH

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.

Update version number in User Guide cover

SPH

Needed by App Freeze.

Contact Katy Gammage or Mary Hrybyk-Keith to update cover page.

Next time: integrate sejda-console to do this automatically.

 Get updated legal statement/license

SPH

In Progress

Needed by Code Freeze.

 Put in order for additional icons

SPH

(if necessary)

Needed by Visual Freeze.

Update info on public-facing websites

TGG

 

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.

 Obtain Release Approvals

SPH

In Progress

Needed by release day.

For Feature Complete (Jan 10)

Feature complete means that all planned features are implemented in the system and ready for final QA.

For Test Freeze (Jan 25)

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)

TBS

Complete all JIRA verifications

(All)


 

   

Preform independent verification that bug fixes address issue and if necessary create test. 

Test Freeze wrap-up tasks

DJC, SPH, JJKP, RQ

See here: http://li394-117.members.linode.com:8090/display/GW/Engineering+Activities

Address all JIRA tickets awaiting feedback

(All)

 

If someone is asking for clarification, provide requested information.

Mark .tc files with requirements and verify traceability to new requirements

(All)

DSC:
RQ:

SPH:  

This is new this year! 

Perform Static Analysis

WCS SPH/MES

 

Run VS analysis tool to identify possible issues

Run Dynamic Analysis tool or other tool that checks for memory leaks

 

 

 

For Visual Freeze (Noon Feb. 8)

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

Notes

Task

Who

Status

Notes

Update About panel

SPH

  1. Update release number (i.e. R2017a).  

  2. Add any new libraries used. 

  3. Update an links.

The code is located in \src\gui\app

Note that the version number is set in GmatGlobal.cpp. 

Update splash screen

SPH

WCS: will be delivered to

us on Friday

  1. Add new contributors

  2. Remove contributors who did not contribute to this release

  3. Design updates

  4. Update SplashScreen.psd in root directory of the gmat public repo  \moredata\graphics\splash

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

  6. Make sure there is a BETA splash as well. 

Move to App Freeze. 

Update icons

N/A

N/A

If there are any updates, additions, deletions.

Including GMATIcon for Welcome Page

Update gmat_startup_file.txt

WCS

l

  • Update formatting, comments

  • Add any additional plugins

  • Switch to release configuration for public startup (comment out alpha plugins)

Make sure to update both internal and public versions and any platform specific versions.

Complete visual updates

(All)

Move to App Freeze. 

For Code Freeze (10 am Feb. 20) 

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 data files

WCS

SPH: Updated the Schatten file, that is manual.  Tested locally.

WCS: Waiting on Mac tests (MES)

DJC:

 

Update eopc04_08.62-now and run smoke tests and SPICE .bpc file (SHOULD be moved to App Freeze)

Go to bin folder in the test system and run RunDataFileTests.m Without running preparegmat().

Update Info.plist and RunGMAT as needed;

and RunGmat.m (test system) if needed

WCS

WCS: hoping someone else can review latest mods?

DJC:   Looks good.  Minor comment sent to WCS.

Need copyright and release number/name at least; Update to default MATLAB version in test system file

Address issues in Static Analysis results

WCS/MES

 

Update license text

SPH

Nothing to do for R2018a

 

Update application/License.txt file.  May be nothing to do since license did not change.

Update copyright and code headers w/ legal statement

SPH

 

 

This tool makes adding paragraphs and changing headers simple.  http://sourceforge.net/projects/findandreplace/

As of R2018a these directories have files that need updating.

public\src (hpp, cpp)

public\plugin (hpp, cpp)

public\application\matlab\

internal\code (hpp,cpp)

we have missed console code... find path and add it here.

Readme file

 

For R2018a, replace this:

// Copyright (c) 2002 - 2017

with this

// Copyright (c) 2002 - 2018

Final bug fixes

(All)

 

 

 

Mark all open bugs as Affects: current release

SPH

 

 

in JIRA, mark all open tickets as affects the current release

Set release name in code

WCS

Change GmatGlobals to use formal release name

Update version number in Cmakelists

DJC

 

 

For App Freeze (10 am Feb. 20) 

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

SPH

SPH:

WCS:

DJC:

 

Update any install and run instructions. 

Update extras folder

SPH

 

Notepad++ syntax coloring file

Update PDF files in docs folder

SPH/DJC

DJC: 

SPH: 

 

 

 

  • Update watermark: "Draft for Release R2016a"

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

  • DJC: Updated all 3.  Please review.

  • SPH: I checked them.

Gather list of compatibility changes since last release

SPH

 

  • Deprecated fields

  • Removed & disabled fields

  • Anything a user would need to know to make R2016b scripts compatible with this release.

Update Release Notes

SPH

 

 

Update screenshots in User Guide

(Feature leads)

SPH:   

DSC: 

 

Test User Guide instructions & code

(Feature leads)

DSC:

SPH:  

  • Tutorials

  • script snippets

  • reference page examples

Update Windows installer package

DSC

 Ongoing

 

Update links in GMAT.ini

SPH

 

  • Help links

  • Welcome page links

This will cause some tests to fail because we update the location of the new user guide URL, before that URL is active (activated after staging).

Update link tests in TestComplete

TR