Versions Compared

Old Version 70

changes.mady.by.user Steven Hughes

Saved on

compared with

New Version 71

changes.mady.by.user Steven Hughes

Saved on

Key

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

...

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 SourceForgeJJKP(/) Update for new release
Upload docs to documentation siteJJKP 
  1. Upload using SSH to http://gmat.sourceforge.net/docs/
  2. Update HTML with new section
  3. Move "latest" pointer to new folder
Post internal & public release files to MESA networkJJKP 2014-05-22: posted internal files only; public files are in build\VS2010_build\R2015a(tick) 

Branch and tag repositories

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

Follow SourceForge's instructions.

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

...