> Without a way to coordinate merges cross-repository, we would see more CI failures and broken builds due to semantically incompatible patches landing on the mainline branch.
Isn't this rather a symptom of code organization or architecture issues? If one needs to coordinate merges of individual parts, doesn't it mean they belong together? Monorepos or clearer versioning of the individual parts would enable independent merges.
Perhaps but it would require a huge amount of refactoring and reorganizing literally thousands of git repositories. MediaWiki is host to a vast number of extensions which are variously developed by teams within the Wikimedia Foundation as well as individual outside contributors. Each extension might have totally different development process and release schedule (or almost no process/schedule at all)
Isn't this rather a symptom of code organization or architecture issues? If one needs to coordinate merges of individual parts, doesn't it mean they belong together? Monorepos or clearer versioning of the individual parts would enable independent merges.