I am investigating ways to speed up the release process.

Unlike our normal (presubmit/merge queue on master channel) builds, we:

• Do not use RBE
• Use a special builder/pool called dart-internal/flutter_release_builders

The way that this builder works is it is a build orchestrator, and spawns many sub-builds (which in turn, spawn even more).

For example, on build 825:

• Linux Production Engine Drone (linux_fuchsia), queued for 0m
• Linux Production Engine Drone (linux_arm_host_engine), queued for 0m
• Linux Production Engine Drone (linux_host_engine), queued for 0m
• Linux Production Engine Drone (linux_host_desktop_engine), queued for 4m
• Linux Production Engine Drone (linux_host_engine_ddm), queued for 4m
• Linux Production Engine Drone (linux_android_aot_engine), queued for 25m
• Linux Production Engine Drone (linux_android_aot_engine_ddm), queued for 4m
• Linux Production Engine Drone (linux_android_debug_engine), queued for 4m
• Linux Production Engine Drone (linux_android_debug_engine_ddm), queued for 4m
• Linux Production Engine Drone (linux_web_engine_build), queued for 4m
• Linux Production Engine Drone (mac_android_aot_engine), queued for 4m
• Mac Production Engine Drone (mac_host_engine), queued for 0m
• Mac Production Engine Drone (mac_ios_engine), queued for 0m
• Windows Production Engine Drone (windows_android_aot_engine), queued for 0m
• Windows Production Engine Drone (windows_host_engine), queued for 0m

Will file some sub-issues for specifically actionable things.