Also sprach Kim Moir: > Requiring Phabricator for code reviews will allow us to improve > code quality by running linters and static analysis tools automatically > on patches. It will also allow us to simplify and standardize our > engineering workflow by reducing the number of request queues that > developers are expected to monitor.
Are there any firm plans to also reduce the number of integration queues? With this change, which products/teams are still relying on r+/r- and inbound? Whilst I don’t have first hand experience, Phabricator has been known to struggle with large patches, such as the result of upgrading cargo dependencies under third_party/rust. Was a bug ever filed on this? _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
