Release Manager Job Description

The release manager is responsible for facilitating the successful execution of the Simultaneous Release Plan and coordinating with participating projects to deliver the Simultaneous Release Artifacts to the Technical Steering Committee for review and approval. 
The release manager participates in the following:
 - Track cross-project activities and action items including Weather, Autorelease, Integration, Test, Documentation, etc.
 - Follow up and verify completion of per project requirements according to the Simultaneous Release Schedule for Milestones, RC, SR dates.
 - Communicate community-wide release related topics including schedule, requirements, blockers, etc.
 - Run release sync meetings and inform relevant parties of issues, red flags, potential breakages.

[WIP] Release Manager's Workflow & Expectations

Monitor that ODL autorelease (AR) build is working, looking at the build history and notify the PTL's on Autorelease failures. The release manager does not need to debug issues on the infra and project issues. 
The Release Manager needs to triage the issue and follow up PTLs and the community to get the issue resolved. Given that we have multiple streams and ongoing releases it would be good to keep track of the build
before an upcoming release to ensure that AR builds are passing.

Identify the RC (release candidate) - This is where we start looking at the blocking issues and then we get a go/no-go from all the projects.

Once we have a RC, the process requires sending an email to the release mailing list asking the project team to verify the failed tests and update the tracking spreadsheet on the release readiness. 
For each major release, we have a separate spreadsheet CSIT results and separate tabs for each release

At one point we decide that one build will be the RC0 which represents the rehearsal to get all the projects into a single distribution. After the code freeze, we have time to stable

• RC1 is where we want to lock the branch

• RC2 is when we start the go/no-go process  

Things we need to track as the release manager:

• Blocking bugs - JIRA severity

• Weather items - breaks in the ODL which are scheduled and should be handled.

• Tracking the check points - only 3 checkpoints which are init, mid and final. 

• Auto release builds - for all the builds we are working on

Update the tracking spreadsheets with the CSIT test results and notifify the build status.

Update the release page with New releases and check points: https://wiki.opendaylight.org/view/Release_Dashboard