A multi-train week sounds like an exciting experiment! My only concern is that if this becomes the new norm, how will development teams ensure there's enough time to QA changes before they are deployed? Currently, my team often very diligently waits until early Tuesday UTC after the branch is cut to +2 a patch, to ensure QA has a full week to test it. With our QA resources shared with other teams, this system is already pushing it. Many changes don't get proper QA until after they've already landed in production.
Perhaps teams should consider doing more QA on Patch Demo, before changes are merged? This works in many cases but not all because Path Demo still has a ways to go before it has feature parity with the Beta cluster. Are there any other recommendations for testing in a prod-like environment before a patch is auto-deployed? Or perhaps we're aiming for a release early, release often cycle where fixes/reverts come as quickly as the bugs appear?
Warm regards