PC

SES

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

• GMT-7835

Old R2020a Notes below:

DSC:  Updated files for R2020a (GMT-7073) for the 3/17/20 build.  The GMAT python utility was used.  Note that one bug in the python utility had to be fixed, GMT-7175.  

Ran RunDateFileTests.m w/o running preparegmat.  Just one error, which from reading the help comments might be OK.  Request SPH concurrence?  Does anything else need to be done?

      SchattenPredict_DistributedSchattenFile [pos err 19.4597, tol 0.01]

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

11/22/2022:  DJC to work this after Valgrind work.  

• 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

JE

12/8/22:  JE to edit the 4 startup files to comment out the alpha plug-ins. 

JE, editing all 6 startup files, will also move the TLE plug-in from ALpha to default.  

Old R2020a Notes below:

• 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

DSC Note 4/13/2020:  After all changes to the code have been made (still have CCB on 4/14 to review DJC ticket), I am going to do one more complete run with all the alpha plug-ins turns turned on.  Is this recommended for Mac/Linux also?). 

• 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.

DSC

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

• Summary of Deprecated fields
  • BatchEstimatorInv renamed BatchEstimator; BatchEstimatorInv still works (was this release or last?)
• Removed & disabled fields
• Anything a user would need to know to make R2022a scripts compatible with this release.
  • BLS MATLAB file format has changed

DSC

DJC

SES

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

12/1/22:  DSC to take one more pass at it.  Then ask everyone for a final review.  When done, change your red x to a green check.  

Old R2020a Notes below:

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

DJC:  Should we also make the HTML for the API and OC subsystems part of the release?  (It's simple, and done via "make html" in the top level Tools folder.)   4/14/20:  SPH said to include if can do so.   

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

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.  

MS:  C-interface stopped building in R2020a. 

• 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).

11/22/2022:  Question:  in the ini file, do we have to update just web links or is it more involved?  Suggest using a file compare utility to compare the R2018a vs. R2020a 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

11/21/22 - Complete

Update truth data in TestComplete

• Truth output
• Command Summary
• Region checks

11/21/22 - Complete

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 R2022a 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)

1/24/23:  Received legal verbiage and updated Readme.txt file.  

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.)

git source code repo:  Completed 1/24/23.

SVN test repot:            Completed 1/24/23

1. Export the trunk code from svn that is used for the release build when that build is started
2. Wait for a go/nogo call from testing on the build
3. Archive the following folder trees into a zip file: src, plugins, build

1/12/23:  Probably to be done by 1/13/23.  COmpleted 1/24/23.

1. Use the same export as used for the source bundle
2. Wait for a go/nogo call from testing on the build
3. Archive the following folder tree into a zip file: application/data

1/12/23:  Probably to be done by 1/13/23.  COmpleted 1/24/23.

Data = gravity files, space weather files, leap seconds, planetary ephemerides, atmospheric files.  

1. Move the zip file to SF
2. Mark as "staged"    (Staged means only Project members can see this.   We forget this step for R2020a)
3. Download the upload and check it.    (DJC did this for R2020a).

1/12/23:  Probably to be done week of 1/23/23.  COmpleted 1/24/23.

1. Move the zip file to SF
2. Mark as "staged"   (We forget this step for R2020a)
3. Download the upload and check it.   (DJC didnt check for R2020a but not considered critical)

1/12/23:  Probably to be done week of 1/23/23.  COmpleted 1/24/23.

DJC/PC

PC

COmpleted 1/24/23.

Download and run after uploading.  For R2020a, DJC downloaded and ran for all 4 (two flavors Linux) o/s below. 

Check checksum for each os and for each package.  

Completed 1/24/23.

Old R2020a Notes below:

Update for new release.  For R2020a, the actual file is not a RST file. 

DJC/PC

DJC/PC

DJC/PC

1. Upload using SSH to http://gmat.sourceforge.net/docs/
2. Update HTML with new section
3. Move "latest" pointer to new folder

COmpleted 1/24/23.

1/12/23:  Probably to be done week of 1/23/23

Note:  When you run the GMAT GUI, the Help/Online Help directs to SourceForge.  

Old R2020a Notes below:

the C-interface capability was not delivered for Mac but was for the other o/s.  (libCInterface.dll is the name of the plug in for Windows).  SourceForge has a broken link for Help for this.  Wendy and Darrel recommend pointing to the API doc here instead. Sean with an assist from DJC will do this. 

SN: pointed the current development link for API to R2020a/api/apiIndex.html

Update links to current development box.   (Either delete content or fix it)

SN: Moved R2020a content to nightly so links are correct.

SEE NOTES IN SECTION BELOW

See instructions here: http://stackoverflow.com/questions/6777327/how-to-manually-set-the-default-download-file-in-a-sourceforge-project

Completed 1/26/2023.

Upload public repo to sourceforge.

• The trick here is to make sure your remote connection is the ssh connection, only available when logged in as a project admin or developer.  Here's a recomemnded set of steps to follow:
  • Clone the SF repo using git: your git GUI's (that is, GitKraken's) equivalent to
    
    git clone ssh://username@git.code.sf.net/p/gmat/git gmat-git
    
    
  • Set the current branch to the previous pushed code branch (e.g. GMAT-R2018a)
  • Add the mesajade repo as a remote to the SF clone.
  • Fetch master from the mesajade remote.  Do not check it out, just fetch it
  • You're still on the sourceforge (e.g. GMAT-R2018a) branch of the SF repo, right?  Good.
  • Branch the SF repo.  Name the new branch for the release (e.g. GMAT-R2020a).
  • Merge all code from the mesajade repo up to the new release's (R2020a) tag into the SF repo.  This should be a fast forward merge.
    (For R2020a, The tag you was commit d17522c9, dated 4/28/2020, with the commit message "Fix for the GOS being NULL in API calls".)
  • Push your new  branch (GMAT-R2020a) to SourceForge.  Optionally. push the tag as well.

Change new branch to be active branch (what is checked out by default - set in Admin-Code).

Completed 1/26/23.  Note:  We made a TEAMS video of this process.  

DJC needs to run doxygen on the latest source code that we are putting on SF.   

Completed 1/26/2023.

DJC created a zip that contained "base" and "gui" folders.    

Using FileZilla, we renamed the old base and gui folders (/home/project-web/gmat/htdocs/docs/nightly) to old_R2020a and gui_R2020a) and then copied over the new base and gui folders.  The file transfer takes a long time.  

Note:  We made a TEAMS video of this process.  

Follow SourceForge's instructions.

(This is a full backup of the project at sourceforge.  Requires person who backs it up to have significant storage space available)

Here is the Rsync command for us:

 rsync -av git.code.sf.net::p/gmat/git.git .

(Can not be done until git repo updated)

2/2/23:  DJC action item.  Backup size is 2.7 GB

Make files visible (i.e., unstaging) on SourceForge

Completed 1/26/23.  

Old R2020a Notes below:

07/21: Made visible at time of posting, as "soft" release.

(For R2020a, we forgot the "staged" step)

Send out release announcement (Snd BCC to avoid "Reply All" spam)

Create R2022a "Release Notes" PDF to send out. 

DSC

DSC/DJC

• Mention GSFC in the announcement
• Don't include large attachments.

Completed 1/25/23.  

Old R2020a Notes below:

Notes 8/5/2020: 

1. Sent email to Sourceforge gmat-info email list but received "this list is for project announcements only, so your message has been blocked" response. 
2. Sent email to Sourceforge gmat-users email list.  Needs Moderator approval.  DJC approved.  Message sent. 
3. Asked Paul M. to send Release announcement to 590-all. 

"Release Notes" was a bit of a hack.  I made a custom Makefile to build a draft document from the UG xml file, and then edited it for formatting and broken User Guide links.  The cover page is the R2018a cover page, with the "20" piece copied over the 18 and then the "a" shifted to the right.  This is not a recommended best practice! 

Suggestions:

• Build the text version first and then paste and edit it into the xml, avoiding the internal link issue
• Make the cover page image document available for editing.  (I suspect it's a Photoshop .psd file with layers.  Or should be.)

Completed 1/26/23.  

At the GMAT Sourceforge website, select the "Admin" section.  Then choose the "Metadata" section.  Make sure to unlock the padlock in the upper right hand.  Update the "Full Description" section and hit "Save."

Completed 1/26/23.  

Go to https://gmat.atlassian.net/wiki/spaces/GW/overview.  Hit the ". . ." button.  View Restrictions to  make sure you have edit privileges. 

See link below.  

https://gmat.atlassian.net/projects/GMT?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page

• 12/2/2024: All tickets associated with R2025a have been marked and those that do not make the final release will be moved to R2025b. 

Completed 1/26/23.  

Added release announcement text here as well.