Release Conductor Role

Release Conductor

Responsible for release trains on a monthly cycle.

• Reading and ordering all status-analysis issues and pull requests
• Grouping issues and pull requests for a release
• Coordinate with the Tech Lead and [Tech Writer](Tech Writer) regarding what information is in the named release
• Assigning developers to issue
• Merging approved / completed Pull Request into the Develop branch
• Creating a Release branch when code is in final testing
• Creating issues and assigning them to Developer for the release
• Merging the Release into the Master
• Creating a Package release when required

Organizing Issues and Pull Requests

The release conductor takes all issues and pull requests of type status-analysis and checks, labels and updates the status on them according to the release train they want to place the changes on. They also coordinate with the Tech Lead to group together work units for the Developer

Once the issue / pull request is analyzed the status-analysis label should be removed and replaced with one of the following

• status-accepted is accepted but not scheduled on a train yet
• status-accepted-assigned status-accepted-unassigned
  is accepted and scheduled on a train. At this point if it is an issue a developer may be assigned to the work unit. If it is a pull request it will be merged into the Develop
• status-declined has been declined, the issue / pr should be closed as well
• status-see-RFC needs an RFC
• status-needs-additional-info needs more details (status-waiting-for-reply should also be added)
• status-waiting-for-reply waiting for a reply from the person who submitted the issue / pull request

The release conductor may apply different topic labels to help coordinate a release