Versions Compared

Version Old Version 45 New Version 46
Changes made by

Joel Parker

djc

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

For this release: Should we branch the repo here, instead of after release? We need to allow people to continue working on unrelated items while release work is ongoing.{warning

Warning

(DJC here)  A better approach going forward would be to merge master into productions, and switch the test system to the production branch.  This probably ought to be done right before building RC1.  The dev team would have 2 options then:

  1. Checkout branches based on what they are working on (i.e. checkout production for bug fixes for the release, and their current clone of master – every one is cloning for new work, right? – for ongoing work)
  2. Alternatively, make bug fixes in master and cherry-pick merge changes into production as bugs are fixed

The former is the better approach, IMO, because it ensures that the bug fix is made on the current code base for the release.

For App Freeze (May 5) 

App Freeze is a freeze on all application bundle files beyond data and code. This includes documentation, sample scripts, stuff in the extras folder, etc.

...

TaskWhoStatusNotes
Bundle source code and upload to SourceForgeDJC*(error)
  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
  4. Move the zip file to SF
  5. Mark as "staged"
  6. Download the upload and check it
Bundle data and upload to SourceForgeDJC*(error)
  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
  4. Move the zip file to SF
  5. Mark as "staged"
  6. Download the upload and check it
Upload Windows installer to SourceForgeJJKP(error)Download, install, and run after uploading.
Upload Windows zip to SourceForgeJJKP(error)Download and run after uploading.
Post README.txt on SourceForgeJJKP(error) 
Post internal & public release files to MESA networkJJKP(error) 

Branch and tag repositories

JJKP(error)At least tag the test system; consider branching also if the burden on the repo is low.
Make SourceForge repository backupJJKP(error)

Follow SourceForge's instructions.

Perform the backup on the Linode server and download the resultant .zip file, since the local network blocks rsync.

* DJC can only do steps 1-3 here because of contractual constraints

Release Day (May 14)

Use "(/)" for the checkmark ((tick)) and "(x)" for the cross ((error))

TaskWhoStatusNotes

Make files visible on SourceForge

SPH(error) 
Send out release announcementSPH(error)
  • Mention GSFC in the announcement
  • Don't include large attachments.
Post release announcement on SourceForgeDJC*(error) 
Post release announcement on GMAT BlogJJKP(error) 
Mark as released in JIRASPH(error) 

This needs to be assigned to a different person; DJC cannot post to SF

Post-Release

Use "(/)" for the checkmark ((tick)).

...