Bug 1572748 [wpt PR 18355] - Remove reference to Reviewable in the test review policy, a=testonly
authorMs2ger <Ms2ger@gmail.com>
Wed, 14 Aug 2019 10:57:56 +0000
changeset 488130 dfd22af82e3558fd242401fdb9fd64960618d201
parent 488129 9b789837be4090a412637b9be0d9e5161e6f5d99
child 488131 0c9c596c83a953c4ee1e529fa3111808c0130189
push id36435
push usercbrindusan@mozilla.com
push dateThu, 15 Aug 2019 09:46:49 +0000
treeherdermozilla-central@0db07ff50ab5 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1572748, 18355
milestone70.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1572748 [wpt PR 18355] - Remove reference to Reviewable in the test review policy, a=testonly Automatic update from web-platform-tests Remove reference to Reviewable in the test review policy -- Don't recommend strongly. -- wpt-commits: ca4839a06320f3452951a7579f16743cc561598b, 27caa8b336e166c8a4017cb4b619803725b1200d wpt-pr: 18355
testing/web-platform/tests/docs/reviewing-tests/index.md
--- a/testing/web-platform/tests/docs/reviewing-tests/index.md
+++ b/testing/web-platform/tests/docs/reviewing-tests/index.md
@@ -17,19 +17,18 @@ suites, test contributions must be revie
 
 The reviewer can be anyone (other than the original test author) that
 has the required experience with both the spec under test and with
 the [general test guidelines](../writing-tests/general-guidelines).
 
 The review must happen in public, but there is no requirement for it
 to happen in any specific location. In particular if a vendor is
 submitting tests that have already been publicly reviewed in their own
-review system, that review may be carried forward. For other tests, we
-strongly recommend using either Reviewable or GitHub's built-in review
-tools.
+review system, that review may be carried forward. For other submissions, we
+recommend using GitHub's built-in review tools.
 
 Regardless of what review tool is used, the review must be clearly
 linked in the pull request.
 
 In general, we tend on the side of merging things with nits (i.e.,
 anything sub-optimal that isn't absolutely required to be right) and
 then opening issues to leaving pull requests open indefinitely waiting
 on the original submitter to fix them; when tests are being upstreamed