On February 28 Bugzilla review flags will be disabled for Firefox and other mozilla-central products and components. From this point forward, all reviews of code changes to mozilla-central should be conducted in Phabricator. Tasks that have been identified as crucial to this transition have been set as blocker bugs to https://bugzil.la/1514775.
---- FAQ Phabricator transition Are we ready for this? The weekly average number of commits to mozilla-central that were reviewed in Phabricator has been hovering around 80% for many weeks now. While the system can always be improved, this number indicates that most engineers are able to use Phabricator effectively. The Engineering Workflow team has discussed this change with the remaining high-volume users of the old workflow to ensure there are no showstoppers with Phabricator. If you think there may be something we’ve missed, please get in touch with us directly. . What products and components will have the review flag disabled? The list includes the Core, Firefox, Firefox Build System, NSS, Geckoview and Toolkit products. It will also include some components of the Release Engineering and Testing products. It is entirely possible that we will miss some products/components, but users should not treat such omissions as invitations to continue to use Bugzilla for mozilla-central reviews. Adjustments will be made over time as necessary. Any code that will be landed to mozilla-central should be reviewed in Phabricator. Why are we making this change? 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. The previous post ( https://groups.google.com/forum/#!topic/mozilla.dev.platform/JKbDxHSaVfM) announcing the general availability of Phabricator has further details and links to documentation. What about uplifts? Initially, only code landing in mozilla-central will be required to be reviewed in Phabricator. Once we have implemented more processes in Phabricator, we will move reviews of all of the mozilla-central “branches” to Phabricator. I have an unusual use case using patches and Bugzilla, how do I use Phabricator to do this? We’ve put together documentation https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html on how to accomplish various common tasks in Phabricator. If you’re doing something unusual that truly can’t be done with Phabricator, you can of course still attach a file to Bugzilla, and use a needinfo or IRC ping to get sign-off from the reviewer. We expect these cases to be exceedingly rare, and ask that developers use Phabricator wherever possible to unlock the benefits described above. Please also reference the Bugzilla actions and their equivalents on Phabricator https://wiki.mozilla.org/Phabricator/Bugzilla_Equivalents documentation. Where can I reach out if I have questions? Please reach out in the #phabricator channel in irc or Slack. Kim _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
