@federicomena Yes, cycle time and commit volume. Speaking from experience these become significant enough bottlenecks that people who are cynical or impatient about the plan will argue for switching back to "merge first, test later". It's astounding but I've seen this play out repeatedly now. Like people who "don't need type systems" and use compile time as their lever in the argument. Failure to do whole system accounting on development process, time lost to broken trees.