Versions Compared

Version Old Version 79 New Version Current
Changes made by

Steven Hughes

djc

Saved on

Key

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

...

TaskWhoStatus

Internal

Status

Notes

Review Previous Build Release R2015b Process Notes

All   
Obtain Release ApprovalsSPHDoneDoneNeeded by release day.
Get updated legal statement/licenseSPHDoneDoneNeeded by Code Freeze.
Update sample scripts
SPHDoneDone

Needed by App Freeze.

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

JJKP

SPH

DoneDone

Needed by App Freeze.

See Writing Release Notes

Update standard descriptive textSPHDoneDone

Needed by App Freeze.

Will be used in User Guide, websites, release announcement.

Update version number in User Guide cover
JJKPDoneDone

Needed by App Freeze.

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

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

Update info on public-facing websitesJJKP(error)(error)

Needed by Release Day.

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

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

Update release announcement contactsSPH  

Needed by Release Day. Located here.

Put in order for additional iconsSPHDoneDone

(if necessary)

Needed by Visual Freeze.

...

TaskWhoStatusNotes
Bundle source code
DJC* (tick)
  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
Bundle data
DJC* (tick)
  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
Upload source bundle to SourceForgeSPH (tick)
  1. Move the zip file to SF
  2. Mark as "staged"
  3. Download the upload and check it
Upload data bundle to SourceForgeSPH (tick)
  1. Move the zip file to SF
  2. Mark as "staged"
  3. Download the upload and check it
Upload Windows installer to SourceForgeSPH (tick)Download, install, and run after uploading.
Upload Windows zip to SourceForgeSPH (tick)Download and run after uploading.
Post README.rst.txt on SourceForgeSPH (tick)Update for new release
Upload docs to documentation siteSPH(tick)
  1. Upload using SSH to http://gmat.sourceforge.net/docs/
  2. Update HTML with new section
  3. Move "latest" pointer to new folder

SEE NOTES IN SECTION BELOW

Fixed "latest download" to point to new exe.SPH See instructions here: http://stackoverflow.com/questions/6777327/how-to-manually-set-the-default-download-file-in-a-sourceforge-project
Post internal & public release files to MESA networkSPH (tick) 

Branch and tag repositories

DJC (tick)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.)
Make SourceForge repository backupSPH 

Follow SourceForge's instructions.

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

...