Confirmed users
1,927
edits
EngineeringProductivity/Projects/Conduit/RoadMap: Difference between revisions
Jump to navigation
Jump to search
EngineeringProductivity/Projects/Conduit/RoadMap (view source)
Revision as of 17:10, 26 June 2017
, 26 June 2017staging repo
(Patch-based Autoland) |
(staging repo) |
||
| Line 1: | Line 1: | ||
[[toc]] | |||
= Phabricator = | = Phabricator = | ||
| Line 16: | Line 18: | ||
When this stage is rolled out, Phabricator and the new autoland services will be available for the use of all engineering. MozReview will be considered deprecated and will be made read-only soon after. | When this stage is rolled out, Phabricator and the new autoland services will be available for the use of all engineering. MozReview will be considered deprecated and will be made read-only soon after. | ||
= Staging repo for public commits = | |||
This release will bring us back to par with MozReview by supporting push-to-review and autolanding of commits to Try and integration/mainline branches. The system will be built in such a way that it can be extended to support confidential commits; however, for this phase confidential patches will still have to go through the standard Phabricator submission process (“arc patch” or the equivalent). This approach means we can work out any problems with the commit-based approach to review and autolanding. | |||
= Staging-repo support for confidential commits = | |||
By using Mercurial bundles as the storage mechanism for the staging repo, and adding access controls, we can support confidential commits, that is, commits that are only accessible to authorized users. In addition, this solves the "too many heads" problem that has plagued Try and would eventually affect MozReview. | |||
At this stage, push support will be fully implemented regardless of the visibility of the patches/corresponding bug. The patch-based autoland will be considered deprecated, and may be fully removed. Standard Phabricator patch submission will be left enabled primarily to support projects that do not use a staging repo (e.g. projects stored in git repos) that wish to use Phabricator for code remove, perhaps in order to support confidential reviews. | |||