MozillaWiki

EngineeringProductivity/Projects/MozReview: Difference between revisions

Page Discussion

EngineeringProductivity/Projects/MozReview (view source)

Revision as of 17:50, 12 December 2014

1,076 bytes removed ,  12 December 2014
Remove more content in favour of readthedocs
(Remove more content in favour of readthedocs)
Line 1: Line 1:
= Status =
= Status =


Requirements for a next-generation code-review tool are settled and
The vast majority of MozReview docs, including current status, how to use, how to contribute, and future plans, are on [http://mozilla-version-control-tools.readthedocs.org/en/latest/mozreview.html Read the Docs].
the design complete.  We're currently fixing up a few last rough edges
before general deployment; see blockers on {{bug|1021929}}:
 
<bugzilla>
  {
    "f1": "blocked",
    "o1": "equals",
    "v1": "1021929",
    "resolution": "---",
    "include_fields": "id,summary,status"
  }
</bugzilla>
 
See also [[Auto-tools/Projects/CodeReviewTool/Deployment|deployment plans]].
 
= Using & Contributing =
 
All usage and contribution docs are on [http://mozilla-version-control-tools.readthedocs.org/en/latest/mozreview.html Read the Docs].


= Background =
= Background =
Line 83: Line 65:


Do '''''not''''' use the new tool for any confidential bugs.  BMO has a rather complex, fine-grained security model, and we need to make sure we can respect that with the new tool.  We haven't put in that effort yet, so Review Board will reject any attempt to publish a review request on a confidential bug, and similarly if a bug is switched from public to confidential, any associated review requests will '''''automatically''''' be completely deleted.  In other words, don't use this system for anything that is or could conceivably become confidential.  We will announce when the system is ready for confidential patches.
Do '''''not''''' use the new tool for any confidential bugs.  BMO has a rather complex, fine-grained security model, and we need to make sure we can respect that with the new tool.  We haven't put in that effort yet, so Review Board will reject any attempt to publish a review request on a confidential bug, and similarly if a bug is switched from public to confidential, any associated review requests will '''''automatically''''' be completely deleted.  In other words, don't use this system for anything that is or could conceivably become confidential.  We will announce when the system is ready for confidential patches.
= The Future =
== More repos, more VCSes ==
We're going to launch with only a couple hg repos, namely mozilla-central and version-control-tools, to make sure everything works properly.  We'll add more hg repos when we verify that everything is solid.
In parallel we'll be working on support for git to allow usage for git.mozilla.org and GitHub repos.
== Landing reviews ==
This model lends itself quite well to the work being done on AutoLand
and hg transplants.  It should be possible to easily, or even
automatically, push the reviewed commits onto the target repository, a
long-sought-after feature that is extremely tricky, perhaps
impossible, with the current patch-based model.
Mcote
Confirmed users
1,927

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/1040463"