GMAT R2026a Release Process
This page is used to track the process and progress of the GMAT R2026a Release.
Release Terminology
Code complete - All scheduled release development life cycle code except for minor bugs are committed to the main repository and their associated test script are committed to the test repository.
Feature complete - all planned features (new requirements, enhancements) are implemented in the system all documentation updates and software configurations are committed to the main repository.
Docs complete (e.g., GMAT UG, API UG, Specs) with exception of minor tweaks.
Software configuration (e.g. GMAT version number in About, updates to welcome screen, updates to data files) complete
90% of new regression tests are complete; if there are bugs, they are mostly minor and cosmetic.
RC0 - Initial Release Candidate that can be generated at the time of Code Complete. RC0 is the first time where customers can exercise the software and provide feedback if there are issues associated with the release.
RC+ - Subsequent releases from RC0 that are feature complete and a potential candidate to be turned into the public release.
Release Lead Roles
Role | Assignee | Authority/Responsibility |
|---|---|---|
Release Manager |
|
|
Build Manager |
|
|
Test Manager |
|
|
Release Risks
This is a list of all risks (opened and closed) related to smooth release of R2026a.
Owner | Status | Description | Resolution |
|---|---|---|---|
EGD | Mitigate | wxWidgets 3.2.9 update being done close to the end of the release development cycle | Mitigating issues as they are found. In the event of a >minor roadblock, a decision will have to be made. |
EGD | Mitigate | python 3.13/3.14 update being done close to the end of the release development cycle | Mitigating issues as they are found. In the event of a >minor roadblock, a decision will have to be made. |
EGD | Mitigate | GUI test updates for wx 3.2.9 being done close to the end of the release development cycle | Mitigating issues as they are found. In the event of a >minor roadblock, a decision will have to be made. |
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.
GMAT R2026a Jira List:
https://gmat.atlassian.net/projects/GMT/versions/11503/tab/release-report-all-issues
Early Tasks (EGD)
These are long-lead early tasks that can be completed before the detailed release cycle.
Use the checkmark () for complete, the yellow clock () for in-progress, and the cross () for an issue.
Task | Who | Status | Instructions |
|---|---|---|---|
Obtain Release Authorization | EGD |
|
Update and Submit SW Release Package via SRS (https://softwarerelease.ndc.nasa.gov/)
|
Update Sample Scripts | JWN OFI: RM |
OFI |
============================ Tracked in https://gmat.atlassian.net/browse/GMT-8502 This includes
Above work ties in with the Release Notes. (Review list above again after Release Notes written).
Needed by Feature Complete Freeze.
Notes/Questions:
|
Write draft Release Notes | EGD/All |
| Needed by Feature Complete Freeze.
|
Update version number in User Guide cover | EGD |
|
Needed by Feature Complete Freeze; see details below. Process to submit graphic requests: open ticket via https://etd-support.ndc.nasa.gov/servicePortal Next time: integrate sejda-console to do this automatically. |
Get updated splash screen | EGD |
|
Needed by Feature Complete Freeze; see details below. Process to submit graphic requests: open ticket via https://etd-support.ndc.nasa.gov/servicePortal |
Put in order for additional icons | EGD |
| 3/2/26; No additional icons needed. Needed by Feature Complete Freeze None needed since not actively updating GUI. |
Update release announcement contacts | EGD |
| Needed by Release Day.
(Includes aerospace professors, ESA, chief technologists at NASA centers) |
Update libraries to current release | PJC/DJC |
| Update the various depends libraries and other software that is used by GMAT. These include but are not limited to: Python, Swig, Boost, wxWidgets, Visual Studio, GCC. Dependency update tickets for the release: |
After Code Freeze (PJC/DJC):
This should be considered in more general terms – after code complete we should build RC0 to iron out kinks early.
Here are some of the possibilities:
deleting CMake cache
re-running configure.py
Deciding what versions of 3rd party software, including Matlab & Python, should be.
Decision made to build with
Matlab R2025b – Latest Version on Windows Build machine
python 3.9, 3.10, 3.11, 3.12, 3.13, and 3.14 versions
wxWidgets version, 3.2.9
VS 2022
Re-cloning the latest version of OFI – [DJC] Last updated 4/29/2024, so should be good. There is a current dependency issue for the OSG code that is not yet resolved.
Running python script for downloading latest data files (see gmat/application/data for details).
Creating CMake configurations for public and internal releases (alpha & and proprietary plugin choices) [DJC] Not sure what this means
Running the sample scripts
The idea is to catch any problems early.
Development of the scheduled functionality is completed and the closeout of the release process can begin.
Use the checkmark () for complete, the yellow clock () for in-progress, and the cross () for an issue.
Task | Who | Status | Notes |
|---|---|---|---|
Write, run, and commit all final test cases. | All |
| After test complete, the test repo is frozen. All tests must be written by this deadline. 4/1/2026: No additional tests are being added for this release 3/7/2025: Dev code freeze occurred at this time 1/28/2025: Nominal dev process has test creation included
|
Code Freeze wrap-up tasks | EGD |
| See here: Wrap Up Testing - GMAT Wiki - Confluence (atlassian.net) Work with Steve S on this. Notes from R2020a: RM: Performed manual GUI Delete & Rename tests on OFI (Ask Ravi to take a look for R2022a) |
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 | SES |
| Req spec: GMAT Requirements.xlsx RTTM: On mesa in nightly test results
Verified by SES on Mar 25, 2026 |
Perform Static Analysis | JJR/DJC |
| Run VS analysis tool (Win) and Valgrind (Linux) to identify possible issues. Tool was run and analysis was done by XXX/XXX and reported on XX/XX/XXXX |
Review all test failures on each OS (Windows, Linux, Mac) | PJC/EFB/RM |
|
|
Review all deferred tests to verify that they are OK to defer. | PJC/SES |
| Look at the daily test results for all 3 o/s. Do a final review right before Test Freeze achieved. Reviewed and updated on Mar 25, 2026 |
Review tests that are not being run to verify that they are OK not to run | PJC/SES |
| R2026a: Timeboxed effort performed with https://gmat.atlassian.net/browse/GMT-8488 and follow-up https://gmat.atlassian.net/browse/GMT-7825 will be tackled in the next dev release cycle Create a list of tests not being run nightly. |
For Feature Complete Freeze (EGD)
Freeze associated with the generation of RC1.
Use the checkmark () for complete, the yellow clock () for in-progress, and the cross () for an issue.
Task | Who | Status | Notes |
|---|---|---|---|
Update About panel | DJC |
The code is located in src/gui/app Note that the version number is set in GmatGlobal.cpp. | |
Update splash screen | PJC |
|
Move to App Freeze. |
Update icons | N/A |
| 12/2/2024: No updates to the icons for the current release. (Use Default) |
Update UG cover image | DJC | Similar to the splash screen | |
Update OpenFramesInterface's About Panel | RM | OpenFramesInterface's About panel with release number and links to OFI Wiki | |
Complete visual updates | (All) |
| Move to App Freeze? |
Update Info.plist (Mac specific) and RunGMAT (shell script on Mac) as needed | RM | Need copyright and release number/name at least - Info_GMAT.plist and RunGMAT | |
Update test system RunGmat.m on Mac if needed | Mac: RM |
| 4/1/2026: RM has made additional updates to the RunGMAT.m in the gmat-test repo but they aren’t needed for the release Update for MATLAB version and Python version as needed. This refers to the files in the SVN test repo, found under bin/+gmatrunner/ This should be before the Freezes-move there for the next release. |
Address issues in Static Analysis results | (All) |
| Results are informational for 2026a to be used to create tickets for work in the next release |
Update license text | DJC | Update | |
Check the compilation output and fix selected warning messages. | Windows: PC Linux: DJC Mac: TBD |
| Mostly related to the number of Windows warnings, but a check should be done for each OS. Reviewed and fixed relevant warnings on Windows. (Linux: None needed for R2026a; some work needed for R2025b) |
Mark all open significant bugs as Affects: current release | CCB (EGD/SES) |
|
in JIRA, mark all open tickets as affects the current release. This can be done via a global change. |
Update version number in Cmakelists | PJC/DJC |
| Do this right before code freeze. Change to the current release version. |