GMAT 2013b Release Process
This page is used to track the process and progress of the R2013a release.
Table of contents
Â
Target Date: August 14, 2013
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 | Internal Status | Notes |
---|---|---|---|---|
Review Previous Build Release R2013a Process Notes | All | Â | Â | |
Get updated legal statement/license | SPH | N/A | N/A | Needed by Code Freeze. |
Update sample scripts | SPH | Needed by App Freeze.
| ||
Write draft Release Notes | JJKP | Needed by App Freeze. | ||
Update standard descriptive text | SPH | N/A | N/A | Needed by App Freeze. Will be used in User Guide, websites, release announcement. Â |
Update info on public-facing websites | JJKP | N/A | N/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 contacts | SPH | N/A | Needed by Release Day. Located here. | |
Put in order for additional icons | SPH | (if necessary) Needed by Visual Freeze. | ||
Configuration audits. |  |  |  | PCA and FCA. New for Release 2015 based on NPR stuff. |
For QA Complete (August 1)
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 |
---|---|---|---|
Verify that all known bugs are checked into JIRA | (All) | Â | |
Complete all JIRA verifications | (All) | Â | |
Complete QA wrap-up tasks | DSC, SPH, JJKP, RQ | Â | |
Address all JIRA tickets awaiting feedback | (All) | Â |
For Visual Freeze (August 1)
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 | Internal Status | Notes |
---|---|---|---|---|
Update About panel | LOJ | N/A | N/A | Â |
Update splash screen | TGG |
| ||
Update icons | TGG | If there are any updates, additions, deletions. | ||
Update gmat_startup_file.txt | JJKP |
All new plugins are added. | ||
Switch to release configuration in script test system | JJKP | Use new 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) | Fixed all visual issues known before Visual Freeze. |
For Code Freeze (August 1)Â
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 |
---|---|---|---|---|
Update EOP files | WCS | Update eopc04_08.62-now and run smoke tests. | ||
Update files w/ updated legal statement | LOJ | N/A | N/A | Â |
Update license text | LOJ | N/A | N/A | Update application/License.txt file. |
Final bug fixes | (All) | Â |
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 (August 1)Â
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 |
---|---|---|---|
Update README.txt | JJKP | Update with major release highlights. | |
Update extras folder | JJKP | Notepad++ syntax coloring file | |
Update PDF files in docs folder | SPH/DJC |
| |
Gather list of compatibility changes since last release | (Feature leads) |
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 | See the R2013b Compatibility Issues document. | |
Update screenshots in User Guide | (Feature leads) | JJKP:Â | Â |
Test User Guide instructions & code | (Feature leads) | JJKP: |
|
Update Windows installer package | JJKP | Â | |
Update links in GMAT.ini | JJKP | Moved from R2013a Visual Freeze Stage
| |
Update link tests in TestComplete | TR |
|
Â
Testing of Release Candidate 1 (August 5-9)
This will start with the 2013-08-01 daily build. Repeat this phase until tests check out. Steve will make the call.
Use "(/)
" for the checkmark () and "(x)" for the cross ()
Task | Who | Status | Notes |
---|---|---|---|
Update README.txt | JJKP | Â | |
Build Windows installer | JJKP/TGG | Version string: R2013b-rc# | |
Bundle Windows zip | JJKP/TGG | Version string: R2013b-rc# | |
Run TestComplete smoke tests | TR | These are tests on the packaged versions of GMAT: the installer and the zip bundle. | |
Run TestComplete system test missions | TR | These are tests on the packaged versions of GMAT: the installer and the zip bundle. | |
Run script test system | JJKP/TGG | 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 scripts | SPH | 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 tests | TR | (For final RC only) |
Notes
- While this cycle is ongoing is a good time to do wiki updates and cleanup.
Stage Release (August 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. Â
Use "(/)
" for the checkmark () and "(x)" for the cross ()
Â
Task | Who | Status | Notes |
---|---|---|---|
Bundle source code and upload to SourceForge | DJC | N/A |
|
Bundle data and upload to SourceForge | DJC | N/A |
|
Upload Windows installer to SourceForge | JJKP | N/A | Download, install, and run after uploading. |
Upload Windows zip to SourceForge | JJKP | N/A | Download and run after uploading. |
Post README.txt on SourceForge | JJKP | N/A | Â |
Post internal & public release files to MESA network | JJKP | N/A | Â |
Branch and tag repositories | JJKP | At least tag the test system; consider branching also if the burden on the repo is low. | |
Make SourceForge repository backup | JJKP | N/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 () and "(x)" for the cross ()
Task | Who | Status | Notes |
---|---|---|---|
Make files visible on SourceForge | SPH | N/A | Â |
Send out release announcement | SPH | N/A |
|
Post release announcement on SourceForge | DJC | N/A | Â |
Post release announcement on GMAT Blog | JJKP | N/A | Â |
Post-Release
Use "(/)
" for the checkmark ().
Task | Who | Status | Notes |
---|---|---|---|
Party! | (All) | Â | |
Print materials | JJKP |
| |
Conduct postmortem review | SPH | This includes gathering feedback, holding the postmortem meeting, and documenting the results. | |
Submit NTR for next release | SPH | Â | |
Spring cleaning | ? | General cleanup of infrastructure:
|
Notes for postmortem
Please add your notes to the R2013b Lessons Learned document.
Compatibility changes
This is a list of compatibility changes since R2013a that need to be captured in the release notes.
?
Creating an RC
- Create the build
- Log into
gs580w-gmat-t4
as "gs580w-gmat-t4\builduser
". The credentials are on the network drive, in theInfrastructure
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.
- Log into
- Create the bundles
- On your local system, navigate to
SourceForge\trunk\build\install\windows-nsis
. There's aREADME.txt
file there that explains things. - Open a MinGW Shell in this directory.
- Run "
make VERSION=R2013b-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. - Copy the four package files to the network:
\\mesa-file\595\GMAT\Builds\windows\VS2010_build
- To clean everything up afterwards, run "
make clean
".
- On your local system, navigate to
- Run the script test system on the internal installer package. See Running the script test system, below.
Running the script test system
In the steps below, "#
" is the RC number and "<config>
" is "internal
" or "public
".
- Log into
gs580w-gmat-t4
as "gs580w-gmat-t4\testuser
". The credentials are on the network drive, in theInfrastructure
folder. - [RC1 only] Start Task Scheduler and disable the "Run Script Test" task. You'll need to run the RC tests manually.
- Uninstall all previous versions of GMAT.
- Install the version being tested.
- Check "Enable MATLAB interface".
- Leave "Associate file types" unchecked.
- Update the test system repo (located at
C:\Users\testuser\Documents\GmatTest
) - In MATLAB (64-bit):
- Run:
>> cd C:\Users\testuser\Documents\GmatTest\bin
- Run (replace
#
with RC number andÂ<config>
with "internal
" or "public
"):>> diary('..\log\R2013b-rc#-<config>.log')
- 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')
- In
C:\Users\testuser\Documents\GmatTest\bin
, copy the appropriate template (autorundef.R2013bInternal.template.m
orautorundef.R2013bPublic.template.m
) to a new name (such asautorundef.R2013bInternalRC1.template.m
) and fill in the values:RunDef.Build
: "R2013b-rc#-<config>
"RunDef.GmatExe
: path to installedGMAT.exe
RunDef.RegressionBuild
: last build date if testing RC1 (look inGmatTest\output
for latest folder, such as2013-07-31
), otherwise, "R2013b-rc#-<config>
"
- Run:
>>gmattest <name of rundef.m>
(e.g.autorundef.R2013bRc1Internal.m
)Â
- Wait until run completes (usually 8+ hours)
- Run:
>>diary('off')
- Run:
- In a Windows
cmd
window, post results to network usingrobocopy
:>robocopy "
C:\Users\testuser\Documents\GmatTest
\output\R2013b-rc#-<config>" "\\mesa-file\595\GMAT\TestResults\win7\R2013b-rc#-<config>" /E /MT /LOG:%TEMP%\robocopy.txt
Issues for RC1
- ???