You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To deliver on the promises on Crescendo release (and according to our branching strategy), future Flow releases must be backwards-compatible - this automation will check execution results of Flow pre-release (including Cadence pre-release) agains prod and alert the engineering team if the difference in execution is detected.
How will we measure success (Key Results)
The goal is 0 future releases deployed to prod without going through the compatibility check, re-executing min of 500K blocks.
Why (Objective)
To deliver on the promises on Crescendo release (and according to our branching strategy), future Flow releases must be backwards-compatible - this automation will check execution results of Flow pre-release (including Cadence pre-release) agains prod and alert the engineering team if the difference in execution is detected.
How will we measure success (Key Results)
Effort estimate
TBD - @sjonpaulbrown, @zhangchiqing
DACI
The text was updated successfully, but these errors were encountered: