Release Lead Roles

Role	Assignee	Authority/Responsibility
Release Manager	SPH	"owns" release, initiates process, creates tracking page, sends daily status updates, tracks issues to completion, makes sure everyone gets their stuff done, brings decisions to CCB/team, maintains tracking page, collects lessons learned, documents process improvements for next release. Must be reachable and preferably in the office during critical stages like creating and testing RCs.
Build Manager	JJKP or LOJ(?)	controls build system, creates RCs, sends RC availability announcements. Must be reachable and preferably in the office during critical stages like creating and testing RCs.
Test Manager	TR	control GUI/script testing for each RC. Must be reachable and preferably in the office during critical stages like creating and testing RCs.

Open Process Questions R2015a

Consider merging to production and test this before next release process
Automate installer packaging
Consider sanity check from mission users' scripts
Feature Freeze/QA Complete/Beta Test must happen earlier (month before code/App Freeze)
- We need to baseline the test results well before release process starts. Probably at Feature Freeze\QA Freeze
- Consider allowing GATS to produce multiple reports from one test run
When should we merge with production and baseline tests?

This is a list of all risks (opened and closed) related to smooth release of R2015a.

Owner	Status	Description	Resolution
RQ	Closed	GMAT function testing is not completed so there could be many unknown issues discovered close to code freeze.	Configured test system to run regression test system in function mode and ran tens of thousands of test.
JJKP	Open	Many failing event location tests. There may be hidden bugs because issues have not been resolved.
DJC	Open	Python interface unstable. Process for testing and integration into nightly build is unclear.
SPH	Open	Space weather file not ready for testing and tests are not written.

All dates are referenced to 12:00 noon EDT.

For example, a deadline of March 15 should be interpreted as March 15, 12:00 noon EDT.

These are long-lead early tasks that can be completed before the detailed release cycle.

Use "(/)" for the checkmark () and "(x)" for the cross ()

Task	Who	Status	Internal Status	Notes
Review Previous Build Release R2015b Process Notes	All
Obtain Release Approvals	SPH	Done	Done	Needed by release day.
Get updated legal statement/license	SPH	Done	Done	Needed by Code Freeze.
Update sample scripts	SPH	Done	Done	Needed by App Freeze. Write examples that demonstrate new functionality Clean up all errors and warnings Remove deprecated fields
Write draft Release Notes	JJKP SPH	Done	Done	Needed by App Freeze. See Writing Release Notes
Update standard descriptive text	SPH	Done	Done	Needed by App Freeze. Will be used in User Guide, websites, release announcement.
Update version number in User Guide cover	JJKP	Done	Done	Needed by App Freeze. Contact Katy Gammage or Mary Hrybyk-Keith to update cover page. Next time: integrate sejda-console to do this automatically.
Update info on public-facing websites	JJKP			Needed by Release Day. See the list of sites. Update this list as well, if necessary. Updated major sites before announcement. Minor ones can be updated a bit later.
Update release announcement contacts	SPH			Needed by Release Day. Located here.
Put in order for additional icons	SPH	Done	Done	(if necessary) Needed by Visual Freeze.

QA complete means that all known bugs are being tracked, all bug fixes are verified and documented, and the release process can begin.

Use "(/)" for the checkmark () and "(x)" for the cross ()

Task

Who

Status

Notes

Verify that all known bugs are checked into JIRA

(All)

JJKP:
RQ:

SPH: