Notice of withdrawal of Vulkan CTS 1.0.0.x and 1.0.1.x

Components: Vulkan

Change-Id: I87ec80e470e72e9a51760fdb1f441099b9c4d3a8

diff --git a/external/vulkancts/doc/vulkan-cts-withdrawal-2017-11.txt b/external/vulkancts/doc/vulkan-cts-withdrawal-2017-11.txt
new file mode 100644 (file)
index 0000000..49fd17e
--- /dev/null
+++ b/external/vulkancts/doc/vulkan-cts-withdrawal-2017-11.txt
@@ -0,0 +1,39 @@
+Dear Adopters,
+
+This announcement provides notification that the Khronos Group Inc. intends
+to withdraw Vulkan CTS 1.0.0.x and Vulkan CTS 1.0.1.x releases.
+
+These releases are being discontinued due to improved quality and coverage
+provided by more recent releases. Once the releases are withdrawn it will not be
+possible to make conformance submissions against these releases.
+
+The Khronos Group recommends updating to Vulkan CTS 1.0.2.x as early as
+possible.
+
+This announcement covers the following tags as listed on
+https://github.com/KhronosGroup/VK-GL-CTS/tags:
+- vulkan-cts-1.0.0.0
+- vulkan-cts-1.0.0.1
+- vulkan-cts-1.0.0.2
+- vulkan-cts-1.0.0.3
+- vulkan-cts-1.0.0.4
+- vulkan-cts-1.0.1.0
+- vulkan-cts-1.0.1.1
+- vulkan-cts-1.0.1.2
+
+More information about Khronos Conformance and withdrawal policies can be found
+in the Khronos Group Conformance Process document
+(https://www.khronos.org/files/conformance_procedures.pdf) Attachment M.
+Please contact the Vulkan CTS TSG chair (alexander.galazin at arm.com) or
+the Vulkan Working Group chair (tom.olson at arm.com) if you have any questions.
+
+Below are some key dates to acknowledge:
+
+2017-11-15 Notice of intent to withdraw Vulkan CTS 1.0.0.x and Vulkan CTS 1.0.1.x
+           distributed via email to adopters.
+
+2018-05-15 The affected releases are withdrawn.
+
+14 November 2017
+Alexander Galazin
+Vulkan CTS TSG Chair