Engineering Workflow/Road Map: Difference between revisions
(Split into current & future, add section on Phabricator) |
(vendor manifests impact) |
||
| Line 21: | Line 21: | ||
Provide a common structure, process, and tools for managing third-party code in mozilla-central. An [https://groups.google.com/forum/?pli=1#!topic/mozilla.dev.platform/-B8MECCeJnM Intent to Require] was posted to dev.platform on 2018/04/10 and finalized on 2018/10/18. Follow the tracking bug ({{bug|1454867}}) for progress. | Provide a common structure, process, and tools for managing third-party code in mozilla-central. An [https://groups.google.com/forum/?pli=1#!topic/mozilla.dev.platform/-B8MECCeJnM Intent to Require] was posted to dev.platform on 2018/04/10 and finalized on 2018/10/18. Follow the tracking bug ({{bug|1454867}}) for progress. | ||
Impact: | |||
* Third-party code in mozilla-central is obvious and easy to find. | |||
* Standard processes to increase predictability of updates to third-party code. | |||
* Tools to ease updates to third-party code. | |||
== Future == | == Future == | ||
Revision as of 23:41, 2 May 2018
Engineering Workflow Road Map
These are the improvements and new services we are currently working on and others that we are considering for the near future (1-2 years). It is subject to change.
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: Switching to Phabricator has a number of benefits:
- 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.
- Some integration with existing tools and processes, balancing complexity and disruption.
- Excellent support from Phabricator's developers (Phacility) and a large user community.
Vendor manifests
Provide a common structure, process, and tools for managing third-party code in mozilla-central. An Intent to Require was posted to dev.platform on 2018/04/10 and finalized on 2018/10/18. Follow the tracking bug (bug 1454867) for progress.
Impact:
- Third-party code in mozilla-central is obvious and easy to find.
- Standard processes to increase predictability of updates to third-party code.
- Tools to ease updates to third-party code.