...
...
...
...
...
...
...
...
...
...
...
...
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.
Release Management Process & Expectations
...
[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 AR failures. As a release manager can’t go into debuging all the infra and project issues problems,
so RM would need to contact the PTLs to triage the problem and notify and follow up with the community to get the issue resolved.
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.
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