You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

 

 

 

Release R2013a

 This page is used to track the process and progress of the R2013a release. It is a tailored implementation of a general release process, so some steps may not be applicable directly to this release.

Table of contents

Target Date: March 01, 2013

Milestones

Visual Freeze (R-10d)

Visual Freeze finalizes all graphical changes to the software, so that screenshots, documentation, and TestComplete can be updated.

  • Update links in GMAT.ini Who: LOJ Status: incomplete
  • Complete visual updates Who: Developers Status: incomplete This includes the GUI panel configuration files, typos, icons and images, and any bugs related to the GUI.
  • Update About panel Who: LOJ Status: incomplete
  • Update splash screen Who: TGG Status: incomplete Update SplashScreen.psd in GmatDevelopment\moredata\graphics\splash, use GIMP to save a flattened TIF file and overwrite splash screen in GmatDevelopment\application\data\graphics\splash
  • Update gmat_startup_file.txt Who: LOJ Status: incomplete Comment out all plugins except (TBD).
  • Modify script test system based on new gmat_startup_file.txt Who: JJKP Status: incomplete
  1. Committed this new autorundef.template.m file.
  2. Manually updated script test system on test machine and resolved conflicts.

Code Freeze (R-5d)

Code Freeze is a freeze on the software itself before final testing.

  • Update EOP files Who: WCS Status: incomplete Update the FK5 EOP file and run smoke tests.
  • Get updated legal statement Who: SPH Status: incomplete
  • Update files w/ updated legal statement Who: LOJ Status: incomplete
  • Final bug fixes Who: Developers Status: incomplete

App Freeze (R-5d)

App Freeze is a freeze on the non-data and non-code application files, like documentation and sample scripts.

  • Update sample scripts to demo new functionality Who: SPH Status: incomplete
    • Write examples that demonstrate new functionality
    • Clean up all errors and warnings
    • Remove deprecated fields
  • Update README.txt Who: JJKP Status: incomplete Review the text in the main README.txt file and update it as necessary.
  • Update PDF files in docs folder Who: SPH/DJC Status: incomplete
  • Add Release Notes to docs Who: JJKP Status: incomplete Write release notes highlighting any new features and known issues, and include as a part of the User Guide
  1. Copy ReleaseNotes_R2012a.xml to ReleaseNotes_R2013a.xml
  2. Count lines of code: Finding added lines of code
  3. Collect features and improvements from NTR, comparing to R2012a. Send email to team asking for additional ones.
  4. Find deprecated fields by creating an svn diff from the last release until now and searching for "deprecated"
  5. Get number of bugs closed since last release
  6. Get number of developers from TortoiseSVN Log Viewer
  7. Number of system tests from latest nightly test results
  8. Include static list of important outstanding bugs in this release
  • Update User Guide Who: JJKP Status: incomplete Update any outdated screenshots. Test common tasks and tutorials.
  • Update Windows installer package Who: JJKP Status: incomplete Update the NSIS build file and the PACKAGING_MANIFEST.txt file
  • Send printed material to TIMS Who: JJKP Status: incomplete

Package and Test (R-2d)

This will start with the (TBD) daily build.

  • Build Windows installer Who: JJKP Status: incomplete Create the NSIS Windows installer.
  • Bundle Windows zip Who: JJKP Status: incomplete Create the binary compressed application package.
  • Run TestComplete regression tests Who: TGG Status: incomplete These are tests on the packaged versions of GMAT: the installer and the zip bundle.
  • Run TestComplete system test missions Who: JMB Status: incomplete These are tests on the packaged versions of GMAT: the installer and the zip bundle.
  • Run script test system Who: SJH Status: incomplete These are tests on the packaged versions of GMAT: the installer and the zip bundle.
  • Test all sample scripts Who: SPH Status: incomplete
  • Send files to TiMS for CDs Who: JJKP Status: incomplete

Stage Release (R-1d)

This is a soft release, putting all the files in place and updating information. Then on release day, we only need to send the announcements.

  • Bundle source code and upload to SourceForge Who: DJC Status: incomplete Here's the procedure followed for this: 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 (For R2012a, also bundle the EventLocator code and include it) 4. Move the zip file to SF 5. Mark as "staged" 6. Download the upload and check it
  • Bundle data and upload to SourceForge Who: DJC Status: incomplete Here's the procedure followed for this: 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 SourceForge Who: DJC Status: incomplete
  • Upload Windows zip to SourceForge Who: DJC Status: incomplete
  • Update info on public-facing websites Who: JJKP Status: incomplete See the list of sites. Update this list as well, if necessary. Use standardized text across all (and release announcement).
  • Review wiki intro text Who: SPH Status: incomplete
  • Update release announcement contacts Who: SPH Status: incomplete
  • Post internal & public release files to MESA network Who: JJKP Status: incomplete

Announce Release (March 1)

  • Make files visible on SourceForge Who: SPH Status: incomplete
  • Send out release announcement Who: SPH Status: incomplete
  • Post release announcement on SourceForge Who: SPH Status: incomplete
  • Post release announcement on GMAT Blog Who: JJKP Status: incomplete

Post-Release

  • Branch and tag repository Who: DJC Status: incomplete
  • Release party Who: all Status: incomplete
  • Conduct postmortem review Who: SPH Status: incomplete This includes gathering feedback, holding the postmortem meeting, and documenting the results.
  • Submit NTR for next release Who: SPH Status: incomplete

Notes for postmortem

Please add your notes to the Release R2013a Process Notes (external link)document.

Compatibility changes

This is a list of compatibility changes since R2012a that need to be captured in the release notes.

  • Spacecraft.CurrA1MJD parameter is deprecated
  • ImpulsiveBurn.V, ImpulsiveBurn.N, ImpulsiveBurn.B parameters are deprecated
  • non-Earth planet NutationUpdateInterval field is removed
  • restricted setting CoordinateSystem Epoch, Primary, Secondary, XAxis, YAxis, ZAxis fields
  • restricted setting CoordinateSystem Origin field 

Finding added lines of code

  1. Download working copies of <SourceForge>/trunk/src and <Jazz>/trunk/code
  2. Download working copies of code from last release
  3. Use cloc to compare C++, C/C++ Header, and C lines of code. Include plugin code from each public release.

 

  • No labels