The Engineering Workflow team is happy to announce the release of Phabricator and Lando for general use. Going forward, Phabricator will be the primary code-review tool for modifications to the mozilla-central repository, replacing both MozReview and Splinter. Lando is an all-new automatic-landing system that works with Phabricator. This represents about a year of work integrating Phabricator with our systems and building out Lando. Phabricator has been in use by a few teams since last year, and Lando has been used by the Engineering Workflow team for several weeks and lately has successfully landed a few changesets to mozilla-central.
Phabricator is a suite of applications, but we are primarily using the code-review tool, called Differential, which will be taking the place of MozReview and Splinter. Bug tracking will continue to be done with Bugzilla, which is integrated with Phabricator. You will log into Phabricator via Bugzilla. We will soon begin sunsetting MozReview, and Splinter will be made read-only (or replaced with another patch viewer). An upcoming post will outline the plans for the deprecation, archival, and decommission of MozReview, with Splinter to follow. I also want to thank Phacility, the company behind Phabricator, who provided both excellent support and work on Phabricator itself to meet our requirements in an exceptionally helpful and responsive way. User documentation on Phabricator catered specifically to Mozillians can be found at https://moz-conduit.readthedocs.io/en/latest/phabricator-user.html. It is also linked from within Phabricator, in the left-hand menu on the home page. User documentation on Lando can be found at https://moz-conduit.readthedocs.io/en/latest/lando-user.html. MDN documentation is currently being updated. At the moment, Phabricator can support confidential revisions when they are associated with a confidential bug, that is, a bug with one or more security groups applied. Lando, however, cannot currently land these revisions. This is a limitation we plan to fix in Q3. You can follow https://bugzilla.mozilla.org/show_bug.cgi?id=1443704 for developments. See http://moz-conduit.readthedocs.io/en/latest/phabricator-user.html#landing-patches for our recommendations on landing patches in Phabricator without Lando. Similarly, there are two other features which are not part of initial launch but will follow in subsequent releases: * Stacked revisions. If you have a stack of revisions, that is, two or more revisions with parent-child relationships, Lando cannot land them all at once. You will need to individually land them. This is filed as https://bugzilla.mozilla.org/show_bug.cgi?id=1457525. * Try support. Users will have to push to the Try server manually until this is implemented. See https://bugzilla.mozilla.org/show_bug.cgi?id=1466275. Finally, we realize there are a few oddities with the UI that we will also be fixing in parallel with the new features. See https://bugzilla.mozilla.org/show_bug.cgi?id=1466120. The documentation lists several ways of getting in touch with the Engineering Workflow team, but #phabricator and #lando on IRC are good starting points. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
