Confirmed users
1,927
edits
Engineering Workflow/Road Map: Difference between revisions
Jump to navigation
Jump to search
transplant
m (Formatting consistency) |
(transplant) |
||
| Line 25: | Line 25: | ||
* Queued landings due to tree closures means developers don't have to be around when they open to land their 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). | * Becomes a common gateway to mozilla-central (and other repos) which allows more process and security improvements (see below). | ||
=== Transplant internal improvements === | |||
The Transplant service is the engine that takes diffs from Phabricator (via Lando) and, until its retirement, MozReview and lands them in the destination repository on behalf of a user. There is some design debt in its architecture and deployability that will benefit future work on related services (particularly Lando). | |||
Impact: | |||
* Lower maintenance costs. | |||
* Easier to develop locally. | |||
* Better support from operations. | |||
=== Vendor manifests === | === Vendor manifests === | ||
| Line 87: | Line 96: | ||
=== Lando and Phabricator backout support === | === Lando and Phabricator backout support === | ||
=== Lando Git support === | === Lando Git support === | ||