Re: The future of commit access policy for core Firefox

On 2017-03-09 4:53 PM, Mike Connor wrote:
>   * Direct commit access to repositories will be strictly limited to
>     sheriffs and a subset of release engineering.
>       o Any direct commits by these individuals will be limited to
>         fixing bustage that automation misses and handling branch merges.
>   * All other changes will go through an autoland-based workflow.
>       o Developers commit to a staging repository, with scripting that
>         connects the changeset to a Bugzilla attachment, and integrates
>         with review flags.

How is this going to work for the use case of being able to land changes
quickly if, according to the judgement of the patch author, the patch
doesn't need to go through the try server, while being able to monitor
the landing and quickly follow up with a fix in case proven wrong?  Will
there still be a tree like inbound where committers like myself still
have full commit access to where they can use their judgement accordingly?