Remove uprev section from CONTRIBUTING.md

It's ChromeOS specific and we just added a separate file for that.

BUG=None
TEST=None

Change-Id: I67e77c3d30e4e4bf456677a13130563c57a87464
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3336216
Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
Commit-Queue: Junichi Uekawa <uekawa@chromium.org>
This commit is contained in:
Dennis Kempin 2021-12-13 14:33:02 -08:00 committed by Commit Bot
parent cd88647f7d
commit 82f9987349

View file

@ -139,24 +139,6 @@ Note: This is different from other ChromeOS repositories, where Verified +1 bit
is set by the developers to indicate that they successfully tested a change. The
Verified bit can only be set by Kokoro in the crosvm repository.
### Post submit uprev flow.
Daily job called Pupr will test the new change through the commit queue (see the
topic
[chromeos-base/crosvm](https://chromium-review.googlesource.com/q/topic:chromeos-base%252Fcrosvm)
for the attempts). The commit queue will test the new crosvm on ChromeOS
hardware, including high level end-to-end tests. Only if all of those pass, the
pinned version of crosvm (as specified in the `CROS_WORKON_COMMIT` in
[crosvm-0.1.0-rXXXX.ebuild](https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/main/chromeos-base/crosvm))
will be used in the Chrome OS build (this is referred to as `crosvm uprev
process`).
Failures here will delay the landing of the change and may cause Google
engineers to revert your change. If there is any other change in Chrome OS that
crosvm uprev needs to be coordinated, please ask your reviewer and find who is
responsible for looking after the uprev so that they can add relevant Cq-Depend
and other metadata.
## Contributing to the documentation
[The book of crosvm] is build with [mdBook]. Each markdown files must follow