Versions Compared

Old Version 68

changes.mady.by.user Joel Parker

Saved on

compared with

New Version 69

changes.mady.by.user Steven Hughes

Saved on

Key

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

...

 
TaskWhoStatus

Internal

Status

Notes
Update EOP filesWCS(tick)(tick)Update eopc04_08.62-now and run smoke tests and SPICE .bpc file
Update tai-utc file & naif LSKWCS(tick)(tick)Update gmat_startup_file with new LSK
Update Info.plist and RunGMAT as neededWCS(tick)(tick)Need copyright and release number/name at least
Update files w/ updated legal statementLOJ (/)(/)
  • Readme file
  • Source code files
Update license textLOJ(tick)(tick)

Update application/License.txt file.  Nothing to do since license did not change.

Update copyright and code headersLOJ  (/)(/)

This tool makes adding paragraphs and changing headers simple.  http://sourceforge.net/projects/findandreplace/

As of R2015a these directories have files that need updating.

public\src (hpp, cpp)

public\plugin (hpp, cpp)

public\application\matlab\gmat_keyword (.m)

internal\code (hpp,cpp)

Final bug fixes(All) (/)  
Mark all open bugs as Affects: current releaseSPHSPH:  (tick)  

...

TaskWhoStatusNotes
Update README.txtJJKP(/)Update with major release highlights.
Update extras folderJJKP(/)Notepad++ syntax coloring file
Update PDF files in docs folderSPH/DJC

DJC: 

SPH:  (tick)

  • Update watermark: "Draft for Release R2015a"
  • Put into application/docs folder, and individual doc source folders
Gather list of compatibility changes since last releaseSPH (tick)
  • Deprecated fields
  • Removed & disabled fields
  • Anything a user would need to know to make R2013b scripts compatible with this release.
Update Release Notes
SPH (tick) 
Update screenshots in User Guide
(Feature leads)

JJKP: 

SPH: (tick)

RQ: (tick)

DSQ: 

 
Test User Guide instructions & code(Feature leads)

RQ: (tick)

DSQ: 

JJKP: 

SPH:  (tick)

  • Tutorials
  • Common Tasks
  • script snippets
  • reference page examples

SPH:  only tested features that changed for which I was FDE

Update Windows installer packageJJKP (/) 
Update links in GMAT.ini

JJKP

(tick)
  • Help links
  • Welcome page links
Update link tests in TestCompleteTR (tick)
  • Help buttons
  • Welcome Page links
  • Help menu links

...

TaskWhoStatusNotes
Update README.txtJJKP

RC1: 

RC2-RC5: N/A

Next time: this should probably be "Update Release Notes" to add outstanding bugs, etc.

Build Windows installer

JJKP (backup: TGG)

RC1: 

RC2: 

RC2-2: 

RC3: (/)

RC4: 

RC5: 

Version string: R2015a-rc#

Next time: build manager should do this

Bundle Windows zip

JJKP (backup: TGG)

RC1: 

RC2: 

RC2-2: 

RC3: (/)

RC4: 

RC5: 

Version string: R2015a-rc#

Next time: build manager should do this

Run TestComplete smoke testsTRRC1RC3: (/)These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run TestComplete system test missionsTRRC1RC3: (/)These are tests on the packaged versions of GMAT: the installer and the zip bundle.
Run script test systemJJKP (backup: TGG)

RC1: 

RC2: 

RC2-2: 

RC3: (/)

RC4: 

RC5: 

Run the internal installer tests on T4 and the public installer tests on Joel's machine. Run .zip bundle tests afterwards on same build to compare.
Test all sample scriptsSPH

RC2RC3:  (/)

RC4: 

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 configuraiton issues are not caught by running on machines used for development.
Run TestComplete full regression testsTR

RC4: 

RC5:

(For final RC only)

...

TaskWhoStatusNotes
Bundle source code
DJC* (/)
  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* (/)
  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 SourceForgeJJKP (/)
  1. Move the zip file to SF
  2. Mark as "staged"
  3. Download the upload and check it
Upload data bundle to SourceForgeJJKP (/)
  1. Move the zip file to SF
  2. Mark as "staged"
  3. Download the upload and check it
Upload Windows installer to SourceForgeJJKP (/)Download, install, and run after uploading.
Upload Windows zip to SourceForgeJJKP (/)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

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.

...