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: April 02, 2013
For Visual Freeze (March 15)
Visual Freeze finalizes all graphical changes to the software, so that screenshots, documentation, and TestComplete can be updated.
|Update links in GMAT.ini|
|Update About panel|
|Update splash screen||TGG|
Switch to release configuration in script test system
|Complete visual updates||(All)|
Is TestComplete set up to test the Help buttons and the Welcome Page links, or do we need to do it manually?
- Do we want to test both Internal and Public versions separately?
For Code Freeze (March 15)
Code Freeze is a freeze on the software itself before final testing.
|Update EOP files||WCS||Update |
|Get updated legal statement||SPH|
|Update files w/ updated legal statement||LOJ|
|Final bug fixes||(All)|
- Are there any other data files we need to update?
For App Freeze (March 22)
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.
|Update sample scripts||SPH|
|Update PDF files in docs folder||SPH/DJC|
|Write Release Notes||JJKP||See Writing Release Notes|
|Update screenshots in User Guide||Engineers|
|Test User Guide instructions & code||Engineers|
|Update Windows installer package||JJKP|
|Send printed material to TIMS||JJKP|
For Release Candidate (March 27)
This will start with the 2013-03-27 daily build.
Build Windows installer
Bundle Windows zip
|Run TestComplete regression tests||TGG||These are tests on the packaged versions of GMAT: the installer and the zip bundle.|
|Run TestComplete system test missions||JMB||These are tests on the packaged versions of GMAT: the installer and the zip bundle.|
|Run script test system||SJH||These are tests on the packaged versions of GMAT: the installer and the zip bundle.|
|Test all sample scripts||SPH|
|Send files to TiMS for CDs||JJKP|
Stage Release (April 1)
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||DJC|
|Bundle data and upload to SourceForge||DJC|
|Upload Windows installer to SourceForge||JJKP|
|Upload Windows zip to SourceForge||JJKP|
|Revise standard descriptive text||SPH||Used on wiki, external sites, release announcement...|
|Update info on public-facing websites||JJKP||See the list of sites. Update this list as well, if necessary.|
|Update release announcement contacts||SPH|
|Post internal & public release files to MESA network||JJKP|
- Do we want users to be able to build a working GMAT from the source code bundle? I think we need to include more directories than are mentioned above. (e.g. application?)
- Why do we need a separate data bundle?
Announce Release (April 2)
Make files visible on SourceForge
|Send out release announcement||SPH|
|Post release announcement on SourceForge||SPH|
|Post release announcement on GMAT Blog||JJKP|
Branch and tag repository
|Make SourceForge repository backup||JJKP||Follow SourceForge's instructions.|
|Conduct postmortem review||SPH||This includes gathering feedback, holding the postmortem meeting, and documenting the results.|
|Submit NTR for next release||SPH|
General cleanup of infrastructure:
- We need a plan for post-release maintenance of R2013a. How do we decide if something's worth making a service release?
Notes for postmortem
Please add your notes to the Release R2013a Process Notes document.
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