TDN: Windows

WCS: Mac

DJC/SK: Linux

GUI: TR

Script: DSC

OpenFramesInterface v1.0 ready for release with GMAT R2020a.
OFI is documented and has been integrated with GMAT's build and test systems.
Sensor Masks are also documented and all GUI tests are complete.

OFI [RM] (23 sample scripts included)

Optimal Control  (9 sample scripts included)

Needed by App Freeze.

• Write examples that demonstrate new functionality
• Clean up all errors and warnings
• Remove deprecated fields

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

See Writing Release Notes

Needed by App Freeze.

Contact Katy Gammage or Mary Hrybyk-Keith to update cover page.

Next time: integrate sejda-console to do this automatically.

Needed by App Freeze.

Contact Katy Gammage or Mary Hrybyk-Keith to update cover page.

Needed by Code Freeze.

Just need to change the year usually.  

(if necessary)

Needed by Visual Freeze.

Needed by Release Day.

See the list of sites. Update this list as well, if necessary.

NOTE 8/6/2020.  This list needs to be updated.  Also, consider a team discussion to delete some websites. 

Updated major sites before announcement. Minor ones can be updated a bit later.

Needed by Release Day. Located here.

DSC will create list based upon SPH's R2018a email. 

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

RM:

1. Update release number (i.e. R2020a).  
2. Add any new libraries used. (DSC sent list of libraries used).  
3. Update an links.

The code is located in \src\gui\app

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

RM: Updated OpenFramesInterface's About panel with release number and links to OFI Wiki

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. 

Still need some icons to include DynamicDataDisplay.  4/9/2020:  Decided to leave icons alone.  (Use Default)

• 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

SPH

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 (SHOULD be moved to App Freeze)

Update Info.plist and RunGMAT as needed

Update for MATLAB version (to default or agreed-upon version) as needed; are other updates needed as well?

MS: MATLAB is set; SNOPT path information is in file, need to run full test with proper version of gfortran.

*** Who is doing this for Linux and PC? They have been done if the tests are running properly. *** 

(DJC)  Linux and Windows do not use a RunGmat file.  That file is Mac specific. 

(WCS) This is the RunGmat.m file in +gmatRunner in the test system, not the script in the Mac bundle.  I suspect linux updates this too - I see it currently pointing to MATLAB 2019 (as it should).

RM:

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

RM: Updated OFI readme containing license info

DJC for SPH

RM:

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/

As of R2020a these directories have files that need updating.

• 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 R2020a, replace to

// Copyright (c) 2002 - 2018

RM: Updated for OFI

Optimal control: NH 

WCS

DJC:

Update any install and run instructions. 

NH: get Linux inputs from DJC , Mac inputs from WCS , make Windows inputs personally . README will mostly link to user guide. Readme updated .

WCS: README.txt updated for Mac; points to User Guide for most information

• Update watermark: "Draft for Release R2020a"
  • doc/SystemDocs/ArchitecturalSpecification/GMAT-Architectural-Specification.tex: \selectfont{Draft for Release R2020a}}}}
    • Rebuild PDF (LateX + DVI->PDF)
  • doc/SystemDocs/EstimationSpecification/GMATEstimationSpecification.tex: \selectfont{Draft for Release R2020a}}}}
    • Rebuild PDF (LateX + DVI->PDF)
  • doc/SystemDocs/MathematicalSpecification/GMATMathSpec.tex: \selectfont{Draft for Release R2020a}}}}
    • 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

WCS

DSC

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

DSC

DJC

MS

SPH

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.  

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)

MES

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 R2020a scripts compatible with this release.
  • BLS MATLAB file format has changed

DSC

SPH

Optimal Control: NH sent to DSC

NH:

DJC:  API Doc 

RM: OFI

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

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

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.   

Test User Guide instructions & code

(Won't be done for R2020a.  Most important to do this when we start deprecating features.)

All.  

Optimal Control: NH

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

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

Update link tests in TestComplete

• Help buttons
• Welcome Page links
• Help menu links

Update truth data in TestComplete

• Truth output
• Command Summary
• Region checks

Update Build package scripts used to create bundles.

Practice creating bundles

Follow instructions in the section called "Creating an RC" at the bottom of this page.  Those instructions are used to create zip and installer packages.  They often require minor updates prior to release.  This step ensures the scripts are updated and we have practiced using them so when it comes time to create RC1 we have made any changes in the scripts for this release. 

Note SPH added this late in R2020a cycle as a lesson learned to do for future releases.

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)

SPH: 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.

Build Windows installer

Bundle Windows zip

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

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

DSC

MS/WS

DJC

Windows.  First run tests on the installer version of GMAT.  Run tests on the .zip bundle tests afterwards on same build to compare.

(On Final RC, this is 4 runs, Windows and Installer for both  internal and external).  Test internal first.  

For R2020a Windows results, see \\mesa-file\595\GMAT\Builds\windows\VS2017_build_64\R2020a\RC2\Test Results folder.   

Mac – RC1 run completed with 3 errors (alpha off), RC2 run is looping through comparators at 1:46 pm 4/30

Linux – RC2 internal is solid on both Linux flavors.

JM 

DJC

MS/WS

Windows

Linux   Note ticket GMT-7245.  Some tests do not run correctly in the test system on Linux; those tests were checked by hand.

Mac

Definition:  This is the set of 48 regression test scripts that take about 5 minutes to run.

Input/Other/API and Input/UnderDevelopment/MatAPITesting

See JM email dated Wed 4/29/2020 12:11 PM for attached file RunAPITests.m.   

MES/WS

JM/DSC

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.

Nav Python Analysis Scripts

Note:  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. 

JM

DJC

Windows

Linux

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.  

(For final RC only)

On Final RC, this is 4 runs, Windows and Installer for both  internal and external. 

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

SN

SN/DJC

SN/DJC

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

R2020a:

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

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)

Follow SourceForge's instructions.

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)

Make files visible on SourceForge

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 R2020a "Release Notes" PDF to send out. 

DSC

DJC

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

• Need distribution list from SPH

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

R2020a:  Not quite sure what is involved.  Will coordinate with SPH.

8/6/2020:  WIki changed.  SPH to investigate.  Need to find list of releases.

Go to JIRA.  Select "Projects" on LHS menu.  Then select "Releases."  Hit ...

Click on Release of interest.  Move unresolved issues to next Release.