Googler facing documentation can be found at go/flutter-release-workflow.
Release engineer is responsible for:
In the past (and possibly in the future) there was a distinction between a release engineer and release manager. For now the responsibilities are the same and we will refer to the person managing the release as a release engineer.
One time setup instructions for new or returning release engineers.
https://github.com/orgs/flutter/teams/flutter-hackers/members
Possibly not required https://ganpati2.corp.google.com/propose_membership?parent=9147533327&child=$me.prod
Ping any current release engineer to add you as an owner and give you publish access. https://groups.google.com/g/flutter-announce/members?q=role:owner&pli=1
TODO include screenshot
From a glinux machine run sudo apt install tool-proxy-client.
tool-proxy-client is the tool that enables/enforces 2 party authorization for controlled builds.
Public and Beta releases and timelines go/dash-team-releases
Release hotline https://chat.google.com/room/AAAA6RKcK2k?cls=7
Controls who can approve 2 party auth requests. https://ganpati2.corp.google.com/propose_membership?parent=100213927583&child=$me.prod
Conductor is a dart command line interface for common release tasks. Its instructions are in README.md.
go/flutter-signing-apple-contracts Also confirm access to valentine entries listed in that doc.
Confirm access to go/release-eng-retros