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

TDN: Windows

WCS: Mac

DJC: Linux

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

GUI: TR

Script: SPH

control GUI/script testing for each RC. Must be reachable and preferably in the office during critical stages like creating and testing RCs.

Release Risks

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

Owner

Status

Description

Resolution

SPH

Closed.

Triage backlog of issues for critical bugs.

Triage nightly failures.

Reviewed issues, checked in two new bu;gs.

DJC

Open

Level of effort for last minute critical issues is not clear

Investigate SDO STK format file changes and TESS Bugs to get better estimates early so we know if we have any issues.

Tasks

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.

Early Tasks

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	Notes
Obtain Release Approvals	SPH	In Progress	Needed by release day.
Get updated legal statement/license	SPH	In Progress	Needed by Code Freeze.
Update sample scripts	SPH		Needed by App Freeze. Write examples that demonstrate new functionality Clean up all errors and warnings Remove deprecated fields
Write draft Release Notes	SPH		Needed by App Freeze. See Writing Release Notes
Update standard descriptive text	SPH		Needed by App Freeze. Will be used in User Guide, websites, release announcement.
Update version number in User Guide cover	SPH	In Progress	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	TGG		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		(if necessary) Needed by Visual Freeze.

For Feature Complete (May 11)

Feature complete means that all planned features are implemented in the system and ready for final QA.

For QA Complete (May 11)

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