Monorepo Progress Updates: Day 2

[John McDole]

Hello Flutter community!

Following up on the merge process between the Flutter Framework and Flutter Engine repositories, we're happy to report that Day 1 went smoothly with only minor hiccups.
Here's a quick overview of the challenges we encountered and how we addressed them:

• Datastore Chicken-and-Egg: Our datastore, which tracks commits, presented a chicken-and-egg scenario during testing in the Flaux repository. We were able to resolve it quickly.
  
• Repository Drift: Minor differences between the Flaux, Flutter, and Engine repositories, which had diverged slightly over the past few months, required some adjustments. We've addressed these and ensured consistency in the Flutter Framework repository.
  
• Presubmit Test Expectations: Some presubmit tests in the Flutter repository expected production builds to be available. This is because the Engine's post-submit used to be available in the Framework's pre-submit. To keep things moving, we've temporarily shifted these tests to post-submit and will work on re-enabling them in presubmit soon.
  

Today, we're focused on the GitHub merge queue. This is a critical component as it's responsible for building production artifacts of the engine. With the monorepo, we'll no longer have an "engine autoroller" that can lag behind several commits.

We expect to have a decision by 4pm on reverting, however we plan on keeping the tree closed a while longer so we can also land the new Dart Format Style changes!

We appreciate your continued patience as we work to fully enable this!

- Codefu and Crew

--

John McDole | Software Engineer | cod...@google.com | 404-939-6889