(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:
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 (
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.
|Update||SPH||Update with major release highlights.|
|Update extras folder||SPH||Notepad++ syntax coloring file|
|Update PDF files in docs folder||SPH/DJC|
Waiting for final user guide.
|Gather list of compatibility changes since last release||SPH|
|Update Release Notes||SPH|
|Update screenshots in User Guide||(Feature leads)|
|Test User Guide instructions & code||(Feature leads)|
SPH: only tested features that changed for which I was FDE
|Update Windows installer package||TGG|
|Update links in GMAT.ini|
|Update link tests in TestComplete||TR|
Testing of Release Candidate 1 (
This will start with the 2014-05-05 daily build. Repeat this phase until tests check out. Steve will make the call.
Stage Release (
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.
* DJC can only do steps 1-3 here because of contractual constraints
Release Day (
(/)" for the checkmark () and "(x)" for the cross ()