Confirmed users
1,927
edits
Engineering Workflow/Road Map: Difference between revisions
→Current: Lando
m (Eliminate some redundancy) |
(→Current: Lando) |
||
| Line 12: | Line 12: | ||
Impact: | Impact: | ||
* One sole tool for review, which allows the Engineering Workflow to concentrate its efforts, and eliminates the need for contributors to learn several tools. | * One sole tool for review, which allows the Engineering Workflow to concentrate its efforts, and eliminates the need for contributors to learn several tools. | ||
* A more intuitive interface than BMO and MozReview, with a contemporary look to appeal to new contributors. | * A more intuitive interface than BMO and MozReview, with a contemporary look to appeal to new contributors. | ||
* Some integration with existing tools and processes, balancing complexity and disruption. | * Some integration with existing tools and processes, balancing complexity and disruption. | ||
* Excellent support from Phabricator's developers ([https://phacility.com Phacility]) and a large user community. | * Excellent support from Phabricator's developers ([https://phacility.com Phacility]) and a large user community. | ||
=== Lando === | |||
[https://lando.services.mozilla.com Lando] is the new automatic code-landing tool integrated with Phabricator. It is (or at least will be) functionally similar to MozReview's Autoland but is designed to be more maintainable and extensible by being less tightly coupled to the review tool. | |||
Impact: | |||
* One-button landing which can be initiated by anyone with appropriate SCM access. | |||
* Queues landings if the trees are closed. | |||
* Becomes a common gateway to mozilla-central (and other repos) which allows more process and security improvements (see below). | |||
=== Vendor manifests === | === Vendor manifests === | ||