Amend Vulkan Conformance Submission Package Requirements

The current practice is that all bugfixes should be merged
into the CTS repo before being used in a submission.
This change promotes this practices to a requirement.

Compontents: Vulkan

Change-Id: I61eef5522aecf97a3d42c49777681eb671affe87

diff --git a/external/vulkancts/README.md b/external/vulkancts/README.md
index 34d1f3e28190be03c597fc019adf33c6b49ada93..3783e601e7919c3e903908cf1b7d4a4e103b2f07 100644 (file)
--- a/external/vulkancts/README.md
+++ b/external/vulkancts/README.md
@@ -230,10 +230,15 @@ as part of the submission package (3). This can be done by running:
 
        git format-patch -o <submission pkg dir> <release tag>..HEAD
 
-In general, bugfixes and changes to platform-specific code (mostly under
-`framework/platform`) are allowed. The commit message for each change must
-include a clear description of the change and why it is necessary. Non-porting
-related changes must be accompanied by a waiver (see below).
+Changes to platform-specific code (mostly under `framework/platform`)
+are allowed. The commit message for each change must include a clear
+description of the change and why it is necessary.
+
+Bugfixes to the tests are allowed. Before being used for a submission,
+bugfixes must be accepted and merged into the CTS repository.
+`git cherry-pick` is strongly recommended as a method of applying bug fixes.
+
+Other changes must be accompanied by a waiver (see below).
 
 NOTE: When cherry-picking patches on top of release tag, please use `git cherry-pick -x`
 to include original commit hash in the commit message.