Important: Engine & Framework Repository Merge - December 17th

[John McDole]

Hello Flutter!

On December 17th, we're starting the process of merging the Engine and Framework repositories into a single, unified repository. This will ensure that code that ships together is built and tested together, improving efficiency and collaboration.

The TL/DR for Framework and Engine developers:

Framework Developers:

• Please hold off on landing PRs starting Tuesday morning, December 17th, as we'll be turning off auto-submit.

• You can continue working on features, but avoid rebasing your work ahead of the monorepo until it's fully migrated.

Engine Developers:

• Please hold off on landing PRs starting Tuesday.

• When the merge is completed; you will need to port your changes over to flutter/flutter which will look like generating a patch and updating the file paths to the new engine/src/flutter path.

What:

Starting Tuesday we will:

• Pause the autorollers into Flutter Engine and the roller of Engine into Framework

• Disable backfilling on CI (we're about to land >43K commits)

• Run the merge-script to get engine history cleaned up and moved over.

• Pull ancillary commits over from flutter/flaux that

  • Enable updates to the Flutter tooling

  • Update  ci.yaml paths, branches, dependencies, etc

• Land the merge into the tree.

We will focus on fixing the dashboard and any build errors that come up during this time. We're allotting 2 days to work on this.

We will email you when the tree is open to commits!

Contingency Plans:

If issues arise:

File an issue with `Monorepo`. We'll have engineers ready to debug and fix most problems. While we've been preparing for this for two months, it's a large change, and things are bound to break. We appreciate your patience.

In case of major issues:

We have a "red-alert" button. which signal the repository is in the unmerged state. This will revert CI, LUCI, and the tools back to their normal operation. No one is going to work over the holidays.