#supportchat channels for questions that don't seem appropriate to use the issue tracker or the internal email address for.
We do need to maintain code quality and standards. There are a few guidelines for collaboration:
The release-tools repository contains useful information about the responsibilities and tasks performed by a release manager.
Because of the volume of work required to get a release out the door, there will be two primary release managers:
Trained release managers, one in Americas and one on EMEA/APAC, will ultimately be in charge of making sure the RCs get created and deployed.
These release managers need to be very vocal if they need help or something is blocking the release candidate (RC)
Trainee release managers will do most of the hands-on work (e.g. cherry-picking, creating RCs, deploying, etc.).
Trainers should allow trainees to do the work, but like a pilot of an airplane they can take over when time becomes critical.
Here is the upcoming and current list of release managers.