(DJC here) A better approach going forward would be to merge master into production, and switch the test system to the production branch. This probably ought to be done right before building RC1. The dev team would have 2 options then:

Checkout branches based on what they are working on (i.e. checkout production for bug fixes for the release, and their current clone of master – every one is cloning for new work, right? – for ongoing work)

Alternatively, make bug fixes in master and cherry-pick merge changes into production as bugs are fixed

The former is the better approach, IMO, because it ensures that the bug fix is made on the current code base for the release.

For App Freeze (

...

Oct.

...

6)

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.

...

Task

Who

Status

Notes

Update README.txt

SPH

SPH:

WCS:

DJC:

Update with major release highlights.

Update extras folder

SPH

Notepad++ syntax coloring file

Update PDF files in docs folder

SPH/DJC

DJC:

SPH:

Waiting for final user guide.

Update watermark: "Draft for Release R2016a"

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

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:

RQ:

DSQDSC:

Test User Guide instructions & code

(Feature leads)

RQ:

DSQDSC:

SPH:

Tutorials

script snippets

reference page examples

SPH: only tested features that changed for which I was FDE

Update Windows installer package

JJKPTGG

Update links in GMAT.ini

TGG

Help links

Welcome page links

Update link tests in TestComplete

TR

Help buttons

Welcome Page links

Help menu links

Testing of Release Candidate 1 (

...

Oct.

...

7-

...

14)

This will start with the 2014-05-05 daily build. Repeat this phase until tests check out. Steve will make the call.

...

Info

title

Notes

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

Stage Release (

...

Oct 20)

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

Task

Who

Status

Notes

Tag All Repos

DJC

At least tag the test system; consider branching also if the burden on the repo is low. (In SVN, tagging makes a branch, so tagging already creates a branch.)

Bundle source code

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

Creating an RC

Log into gs580w-gmat-t4 as "gsfc580gmatbuild". The credentials are on the network drive, in the Infrastructure folder.

Start Task Scheduler.

[RC1 only] Disable the "GMAT Daily Build" task, so it doesn't run automatically during the RC cycle (this can make things overly confusing).

Manually run the "GMAT Daily Build" task.

Create the bundles

On your local system, navigate to GmatDevelopment\build\install\windows-nsis. Note that you do not need to pull files down from the Git repository; this process will pull files from the remote build and create the packages in your local directory. There's a README.txt file there that explains things.

Open a MinGW, MSYS2, or Cygwin shell in this directory.

Run 'make assemble VERSION="R2015a-rc#"', where "#" is the number of the RC you're creating. This will create two directories in the current directory: gmat-internal and gmat-public.

Run the following commands to add the User Guide cover. This requires sejda-console.

Run 'make VERSION="R2015a-rc#"', where "#" is the number of the RC you're creating. This will create four packages in the current directory: A .zip and a .exe file for both the internal and public versions. Note: To create only an internal version, run 'make internal VERSION="R2015a-rc#"'.

Copy the four package files to the network: \\mesa-file\595\GMAT\Builds\windows\VS2013_build_32\R2015a