...
- [ SPH ] There are release processes that should be moved to development processes so they occur early and ensure nightly builds are as near release as possible. Requirements migration, RTTM mapping, wrap up tests, xml and rst docs.
- [ SPH ] Keep tests in release configuration. There are too many config changes late in release that hurt us. Cycle through config such as internal, public, alpha during weekly or monthly regression tests so taht we are always testing the different configurations.
- [ MES ] Add/move tasks to be accomplished to attain feature complete milestone
- Merge of key branches into master, after first merging master into branches and running tests – at the very least smoke tests in the branch before merging back to master
- Updating the data files with GMAT python utility (now 1st task on Code Freeze list)
- Move all new test scripts that are complete at this point into gmat_test/test/script/input
- Move all new sample scripts that are complete at this point into gmat/application/samples
- Create an RC0 on each platform with new capabilities as they stand, internal plugins and alpha plugins all included – in short, everything included; then run nightly build tests.
The idea here is to have a "super-smoke test" at the beginning of release testing to identify issues early.
Stop Doing
- [ SPH ] The number of permutations of different packages is too large, zip, installer, public, internal, mac, linux, windows. I propose we consider only releasing a zip or installer on Windows to reduce the number of permutations of tests to run.