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

Change new branch to be active branch (what is checked out by default)

.

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