• EGD

• "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 during critical stages like creating and testing RCs.

• Windows: PJC
• Mac: PJC
• Linux: DJC

• Controls build system, creates RCs, sends RC availability announcements.
• Must be reachable during critical stages like creating and testing RCs.

• GUI: Tetyana
• Windows Script: PJC

• Control GUI/script testing for each RC. 
• Must be reachable during critical stages like creating and testing RCs.

• 2/21/25: Approved for release
• 1/15/25: NTR approved and submitted SRS docs
• 1/06/25: Currently awaiting NASA Approval and Case Number 
• 12/09/24: Submitted R2025 New Technology Report (NTR) via E-NTR System (https://invention.nasa.gov/), includes a 10-day Innovator Review Cycle.

Update and Submit SW Release Package via SRS (https://softwarerelease.ndc.nasa.gov/)

• Software Release System (SRS) routes package through multiple reviews: 
  • POC Review
  • Initial SRA Review
  • Technology Transfer Office Review
  • Patent Counsel Office Review
  • IT Security Review
  • Export Control Office Review
  • Section 508 Coordinator Office Review
  • Other Review
  • Final SRA Review

Defer until 2025b

• MM/DD/YY: TBD

============================

This includes

-Ask SES if he think any more sample scripts needed.  

-Generic GOES sample scripts.  (Dont use GOES orbit or other data, generic torque recall, etc).

Jairus (Ground station masking, cov prop, IOD, TLE prop, Trk 2-23)

Steve S/Pete C (SAA sample script)

Above work ties in with the Release Notes.  (Review list above again after Release Notes written).  

Needed by App Freeze.

• Write examples that demonstrate new functionality
• Clean up all errors and warnings
• Remove deprecated fields
• Make sure all the old and new sample scripts run correctly.  (Note: There is a way to run all scrips in a folder, must be in Run_Mode=Testing)

Notes/Questions:  

1. The OFI scripts are stored in the OFI repo, not in the GMAT repo. That's because OFI is an externally maintained and managed project.When GMAT is built, e.g. the windows build machine, it copies the OFI sample scripts into latestcompleteversion. That's how those scripts will be part of the release without being in the GMAT repo.
2. The sample script file names be pre-pended with R2022a_
3. Make sure all the API Folder (and associated sub-folder) sample scripts are updated and run correctly.
4. Starting with R2021a:  For Nav, we will be adding python analysis scripts associated with the EKFS GPS point solution tutorial, to the GMAT releases.  Thus, in addition to the usual GMAT sample scripts, we should be making sure that the non-GMAT scripts, such as these python analysis scripts, also still run correctly. 

Needed by App Freeze.

• 2/20/2025: Team compiling release note updates in draft in team document repository

See Writing Release Notes

Needed by Visual Freeze; see details below.

Process to submit graphic requests:  open ticket via https://etd-support.ndc.nasa.gov/servicePortal

• 1/21/2025: EGD-Uploaded graphics artifacts to the internal document repository release folder under the management tab
• 12/2/2024: Created ETD graphics ticket 78067 for splash screen and user guide cover graphics update

12/2/24;  No additional icons needed.  

Needed by Visual Freeze

None needed since not actively updating GUI.  

Needed by Release Day. 

Located here (Who owns this Google Drive document?). Recommend moving to the internal GMAT team document repository

(Includes aerospace professors, ESA, chief technologists at NASA centers)

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:

• GMT-5612
• GMT-8161 

After test complete, the test repo is frozen.  All tests must be written by this deadline.

3/7/2025: Dev code freeze occurred at this time

1/28/2025: Nominal dev process has test creation included

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

EGD: This is part of the process for closing a ticket and is a redundant step

(All)

SES

Run VS analysis tool (Win) and Valgrind (Linux) to identify possible issues. 
(Note that the requirement here is just to "run" the tool.  Analysis can come later.)

Tool was run and analysis was done by JJR/DJC and reported on 3/14/2025

EGD: Redundant step if following nominal dev process

1. Update release number (i.e. R2025a).  
2. Add any new libraries used. (Did we update any libraries for R2025a since R2022a?).  
3. Update any links.

The code is located in src/gui/app

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

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. 

12/2/2024: No updates to the icons for the current release.  (Use Default)

Update Open Frames Interface's

About Panel

OpenFramesInterface's About panel with release number and links to OFI Wiki
(Panel is accessed from the OFI configuration panel; still says 2022a; likely okay for this release though)

Update Info.plist (Mac specific) and RunGMAT (shell script on Mac) as needed

Need copyright and release number/name at least - Info_GMAT.plist and RunGMAT

Mac: PJC/JG

Linux: DJC

Update for MATLAB version (MatLab R2022) and Python version (Python 3.9) 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.

Not going to fix anything for 2025a

DJC

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

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 R2025a; some work needed for R2025b)

CCB

(EGD/SES)

Do this right before code freeze.  Change to the current release version.  

Change GmatGlobals to use formal release name and do a scan of all files to make sure the current release version is being referenced throughout the code

• Verify proper release name in batch estimator and Kalman filter report file banners

DJC/PJC

Note that the requirement here is just to "run" the tool.  Analysis can come later.  

Note: This involves running the Valgrind tool

DJC

(All)

Note: this must be done after CCB has accepted all final changes and we are ready to create RC1.  It requires coordination with the entire team as almost all source code files will be changed. 

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

Double check the following directories for changes:

• public\src (hpp, cpp)
• public\plugin (hpp, cpp)
• public/plugin/CInterfacePlugin/matlab
• public\application\matlab\
• internal\code (hpp,cpp)
• Readme file

  Updates for 2011 onwards were needed.  Files that assert copyright outside of the GMAT project were not updated.  Files with no copyright header at all were also not caught (there are at lest some - in the CsaltCWrapper code.  THere is likely more as well.

For R2025a, replace to

// Copyright (c) 2002 - 2025

SES

PC to run GMATDataFileManager.py locally and then copy files over to source code git repo.  See 

• GMT-7835

Update Schatten data file (SES has updated file ready)

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

  (3/11/2025)

R2025a additions

• Other pieces that needed updating:
  • API User's Guide
  • Optimal Control Spec
  • API/OC combined HTML files
• For the next release:
  • API Cookbook

OLD Notes from R2022a

• Update watermark: "Draft for Release R2022a"
  • doc/SystemDocs/ArchitecturalSpecification/GMAT-Architectural-Specification.tex: \selectfont{Draft for Release R2022a}}}}
    • Rebuild PDF (LateX + DVI->PDF)
  • doc/SystemDocs/EstimationSpecification/GMATEstimationSpecification.tex: \selectfont{Draft for Release R2022a}}}}
    • Rebuild PDF (LateX + DVI->PDF)
  • doc/SystemDocs/MathematicalSpecification/GMATMathSpec.tex: \selectfont{Draft for Release R2022a}}}}
    • Rebuild PDF (LateX + DVI→ PS, PS->PDF)
• Put into application/docs folder, and individual doc source folder
  • Copied the 3 newly generated PDFs into application/docs

All

Old R2020a Notes below:

• editing all 6 startup files, will also move the TLE plug-in from Alpha to default.  
• Switch to release configuration for internal startup (comment out alpha plugins in the internal startup files.  This is just 2 files)

Make sure to update platform specific versions.

Question: Should this happen after testing of internal build is complete (i.e. right before packaging)?  The issue is that these need to be ON for thorough testing, but not ON in the delivered application

• Update formatting, comments
• Add any additional plugins
• Switch to release configuration for public startup.  See here for instructions.

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

EGD

N/A

No new alpha plug-ins for R2025a.

Verify that the test system has been updated  to identify new internal and alpha features for this release.  (e.g., make sure GetAlphaScriptContent.m as been updated.  Note:  This should be updated by TestComplete).

Update local test configurations to test only production features (don't test alpha plugins).  (e.g., for Windows, in file autorundef_T6.m, set "runDefMan.SetRunAlphaTests(false) ")

Instructions for performing those two steps are located here. 

Note:  This is done immediately before release testing.  

Old R2020a Notes below:

DSC Note 4/13/2020:  I updated GetAlphaScriptContent.m for known Nav alpha Resources and Commands.  Are there any other alpha Resources and Commands for R2020a?

Gather list of compatibility changes since last release

(part of Release Notes)

SES

The draft release notes are up-to-date.

• Summary of Deprecated fields
  • BatchEstimatorInv renamed BatchEstimator; BatchEstimatorInv still works (was this release or last?)
    • This still works
  • The only new deprecated parameter is BatchEstimator MatlabFile. This is mentioned in the release notes.
• Removed & disabled fields
  • None
• Anything a user would need to know to make R2022a scripts compatible with this release.
  • Some measurement paths have changed, but the old path format still works. This is already mentioned in the release notes

EGD

DJC

SES

PJC

RM: OFI

To Create JIRA Release notes link that is used in Release Notes, see instructions here:

https://confluence.atlassian.com/adminjiraserver/creating-release-notes-938847219.html

Old R2020a Notes below:

Make sure SPHINX documentation for API and OC are included in docs folder 

Make the HTML for the API and OC subsystems part of the release, if possible 

https://docs.google.com/document/d/1Uy2ZlKLUBPNBdySQPLI-rmibcmRRqX1T8BbPqSsZ8Hg/edit#

• 3/6/2025: EGD - Updates to UG should have been made with the work with the tickets
• 3/11/2025:  DJC - There are a few screen shots in the Architectural spec that are clearly quite old and need an update

Test User Guide instructions & code

(Not much to be done for R2022a.  Most important to do this when we start deprecating features and parameter names.)

PJC

• Tutorials
• script snippets
• reference page examples
• Update UG to take into account compatibility changes.  

• Help links (Need to put help pages on sourceforge in order for the web links to work)
• 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).

Suggest using a file compare utility to compare the previous release vs. current release GMAT.ini file.  

NOTES

(1)  For LInux, all the help (e.g., "Links and Resources" and the Help button for a Resource) use the HTML pages on sourceforge.  Linux does not support Windows Help.  

(2)  For Windows, the Help button for a Resource uses the file \docs\help\help.chm.

Update link tests in TestComplete

• Help buttons
• Welcome Page links
• Help menu links

Update truth data in TestComplete

• Truth output
• Command Summary
• Region checks

Get updated legal statement/license

This is usually done as the final step before app freeze.  Basically:

• Get OK from lawyers.  e.g., is it ok to just change the date?
• Work work work until there are NO MORE CODE CHANGES needed for RC1.
• Tell all developers that they are done.  No more R2025a code changes will be accepted.  Get dev team buy-in. (NO MORE CODE CHANGES.  REALLY!)
• Run a script that updates the copyright line in all source files (Darrel has done this for the last 3 or 4 releases - before that, there was ALWAYS something missed.)
• Commit the updated files to the repository
• Build the release candidate RC1
• Tag the code as RC1 (may happen before the previous bullet)

PC

DJC

This needs to be provided once the documentation is complete and built with the release candidate.  Note this cannot be done until all docs are frozen!   (SPH takes Windows RC, edits Help doc in Acrobat.  Sends to Mac/Linux)

Rebuild the OC/API HTML Help

PC 2022a help folder on mesa file and SharePoint. Ask PC for location. 

Old R2020a Notes below:

DJC: Make sure SPHINX for API and OC are included.   DJC added the files to application/docs. 

Note: For future releases, we should consider adding a build step to generate these automatically as part of the install process in CMake, rather than putting the generated files into the repo directly.

Bundle Windows zip

Is there anything to this besides putting the build in a zip? Steps for Mac/Linux here too?

For Windows, see gmat\build\install\windows-nsis\CreateInstall.bat

To be placed on Mesa-files

These are tests on the packaged versions of GMAT:  the zip bundle.  ( Test internal first. )

(Current smoke tests take a long time, about 4 hours.  Maybe later, cut this time down)

DSC/PJC

DJC

EGD

PJC

DJC

At a minimum these need to be run individually by hand or run in GUI regression system. 
Additionally, they must be run on a system that has no other installations of GMAT.  Past experience has shown that missing files, and configuration issues are not caught by running on machines used for development.

PJC

DJC

Windows

Linux, /3/23 Action for DJC

See GMT-8333.  This call is used in Ex_R2020a_RangeMeasurement.py.  All other Python examples run correctly.

Mac,  1/3/23 Action for AC.  

Old R2020a Notes below: 

Notes: 

(1)  Make sure all API Sample tests (API folder and API/Jupyter sub-folder) run correctly.  

(2)  For 2020a Mac, will not run API sample scripts.  

Definition:  Run scripts in Folder API and API/Jupyter.  

Run sample missions using GMAT.exe, monitor the runs, and document any anomalous behavior. 

Windows

Instructions for running sample scripts from the GUI using Testing Mode.

• To run a folder of scripts you have to be in TESTING mode, # Debug options
  #-----------------------------------------------------------
  RUN_MODE              = TESTING
• Then highlight "Scripts" in GUI
• Right Click to "Add Script Folder"

SES

BM

(For final RC only)

On Final RC, this is 2 runs, Windows both internal and external. 

Save artifacts related to RC testing.  This includes matlab test scripts used and test results. 
For an R2020a example, see \\mesa-file\595\GMAT\Builds\windows\VS2017_build_64\R2020a 

BM to start working on NTR for our next (single customer) release.  Try to word it so fixes/enhancement for follow-on builds are covered.  Proposal

• Put in NTR for R2023a Beta
• As before, we will have SUAs with multiple customers and multiple deliveries using this single NTR.  
• Get OK from legal that one of the Beta deliveries to NOAA/GOES will actually be "non-Beta."

Windows

LInux

Mac

Review all tests not being run and ensure all tests are being run for the next release (In particular the 'R2023a' category)

2/2/23.  R2023a is now turned on for Windows. 

Please add your notes to theR2025a Lessons Learned document.