Engineering Workflow/Road Map: Difference between revisions

Engineering Workflow/Road Map (view source)

Revision as of 01:41, 12 July 2018

304 bytes removed , 12 July 2018

move a couple items to Done

Mcote

Confirmed users

1,927

edits

@@ Line 4: / Line 4: @@
 == Current ==
-=== Phabricator integration ===
-Although our [[Phabricator]] instance has been up since September 2017, there has been ongoing work to integrate it into our tools, most notably [[BMO]].  There is a tracking bug ({{bug|1381498}}) for the remaining work before we announce general availability and start encouraging people to move over.
-The last remaining item of note is forking Arcanist so that it works with git-cinnabar ({{bug|1443375}}).
-Impact:
-* One sole tool for review 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.
-* 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.
-=== Lando initial release ===
-[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 offers an easier way to land code and minimal context switching from reviewing code.
-* Queued landings due to tree closures means developers don't have to be around when they open to land their code.
-* Becomes a common gateway to mozilla-central (and other repos) which allows more process and security improvements (see below).
 === Transplant internal improvements ===
@@ Line 123: / Line 102: @@
 === Artifact caching experiments for builds ===
+== Done ==
+=== Phabricator integration ===
+The bulk of Phabricator integration into BMO was completed in May.  Phabricator is now available for general usage.
+Impact:
+* One sole tool for review 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.
+* 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.
+=== Lando initial release ===
+[https://lando.services.mozilla.com Lando] is the new automatic code-landing tool integrated with Phabricator.  It is 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 offers an easier way to land code and minimal context switching from reviewing code.
+* Queued landings due to tree closures means developers don't have to be around when they open to land their code.
+* Becomes a common gateway to mozilla-central (and other repos) which allows more process and security improvements (see below).