Vulkan-docs: Task list for Vulkan 1.2 release

[TomOlson]

Vulkan 1.2 promotes 23 previously released Vulkan extensions into a new core specification, and adds other minor features to improve integration and ease of use. The complete list of new features can be found in Appendix D of the specification.

Vulkan is an ecosystem-driven API; the Vulkan and SPIR-V Working Groups define the specification, but the tools developers need to use the API come many teams across the Vulkan community. This issue tracks the state of the various documents and software artifacts needed to develop Vulkan 1.2 applications. As each item is made public, the task will be checked off below. When all tasks have been checked off, this issue will be closed and the Vulkan 1.2 release will be complete. Unless otherwise noted, the target release date for all items is on or before January 31, 2020.

The task list for the Vulkan 1.2 release is:

• [x] Vulkan specification: https://www.khronos.org/registry/vulkan/#apispecs
• [x] Vulkan headers: https://github.com/KhronosGroup/Vulkan-Headers
• [x] SPIRV-Tools: in master now, was KhronosGroup/SPIRV-Tools#3137
• [x] glslang support: in master now, was KhronosGroup/glslang#2058
• [x] shaderc support: https://github.com/google/shaderc
• [ ] DXC support: target time frame: 1H 2020
• [x] Validation Layer support: https://github.com/KhronosGroup/Vulkan-ValidationLayers/tree/v1.2.131
• [x] Loader support: https://github.com/KhronosGroup/Vulkan-Loader/tree/v1.2.131
• [x] Tools support: https://github.com/KhronosGroup/Vulkan-Tools/tree/v1.2.131
• [x] Vulkan 1.2 SDK: https://vulkan.lunarg.com/
• [x] Vulkan 1.2 Conformance Test Suite (CTS): https://github.com/KhronosGroup/VK-GL-CTS

Public installable Vulkan 1.2 drivers are available for download from the following vendors at the supplied URLs:

• AMD: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-1-2
• Intel (Windows 10): https://downloadcenter.intel.com/download/29335/Intel-Graphics-Windows-10-DCH-Drivers
• NVIDIA: https://developer.nvidia.com/vulkan-driver

Source code for Mesa drivers from Intel (for Intel GPUs) and from the Mesa RADV team (for AMD GPUs) can be found at https://gitlab.freedesktop.org/mesa/mesa/

[hakzsam]

@TomOlson RADV MR https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3410

[jekstrand]

Please, people, when you edit the task list, make sure you refresh your page immediately before hand. Edits are getting lost left and right. Either that or only @TomOlson should edit. We also appear (from what I'm seeing) to also be seeing a failure of the gitlab MR edit draft system where even if you do refresh stuff may get lost when you click "edit". You have to edit then discard then edit again to get a proper refresh. :frowning_face:

[jekstrand]

@TomOlson RADV MR https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3410

Both RADV and Intel Linux have now been merged into mesa master.

[dneto0]

SPIRV-Tools support: https://github.com/KhronosGroup/SPIRV-Tools/pull/3137

[gnl21]

The glslang link looks wrong. The correct link is: https://github.com/KhronosGroup/glslang/pull/2058

[oddhack]

Please, people, when you edit the task list, make sure you refresh your page immediately before hand. Edits are getting lost left and right. Either that or only @TomOlson should edit. We also appear (from what I'm seeing) to also be seeing a failure of the gitlab MR edit draft system where even if you do refresh stuff may get lost when you click "edit". You have to edit then discard then edit again to get a proper refresh.

Ditto. I keep trying to click the "headers" item as being done and it appears to reflect it, then I come back to the page later and it's back to unchecked. Seems like Github needs better locking around updates.

[johnkslang]

But, some of this could be browser caching, and the browser submitting older versions as the update, which GitHub can't control.

I re-clicked the headers for you, see how long it sticks.

[johnkslang]

The glslang link looks wrong. The correct link is: KhronosGroup/glslang#2058

I'm sure I had 2058 to begin with, will carefully try updating again, once bots finish, with the new location.

[jekstrand]

But, some of this could be browser caching, and the browser submitting older versions as the update, which GitHub can't control.

GitHub could make it so that an edit sends both the new text and what it thinks the old text was and do an atomic_compare_exchange. You'd still have the ABA problem but at least it'd be better. Also, they clearly have the history of all edits so they could send along which edit the current one is based on and reject if it doesn't match. :smile: Even Bugzilla manages to get this right.

[oddhack]

Also, they clearly have the history of all edits so they could send along which edit the current one is based on and reject if it doesn't match. Even Bugzilla manages to get this right.

If only GH had access to some sort of "revision control" software that would keep track of changes and could tell when conflicts arose... naah, dreaming again.

[johnkslang]

I've updated check-off items for Vulkan headers, glslang, and SPIRV-Tools, as well as the location of the latter two. All seem to be sticking and didn't seem to lose anything.

[dneto0]

Shaderc support in https://github.com/google/shaderc/pull/958

[krOoze]

But, some of this could be browser caching, and the browser submitting older versions as the update, which GitHub can't control.

It could. Though I think the post editing is mostly meant for moderation, not for collaboration.

PS: there is a Projects feature, which you could try to use for this instead, maybe.

[TomOlson]

Definitely issues arising between browser caching and how the GH site behaves. But let's take those inside Khronos - not very interesting for people trying to track the Vulkan 1.2 release. Next time we do this, we'll find a different mechanism.

[dneto0]

Shaderc support has been merged into its master.

@TomOlson: please check the boxes for Shaderc

[alegal-arm]

CTS: https://github.com/KhronosGroup/VK-GL-CTS/releases/tag/vulkan-cts-1.2.1.0

[mikew-lunarg]

Validation layers: https://github.com/KhronosGroup/Vulkan-ValidationLayers/tree/v1.2.131

[TomOlson]

I have deleted the "GLSL specification" deliverable - turns out there are no updates.

[mikew-lunarg]

SDK released 2020-01-28

https://vulkan.lunarg.com/

[oddhack]

@TomOlson do you know who owns the DXC support checklist item and/or its status? Unlike the others there's no outward link to that repo, or owner, but it was supposed to be resolved 6 months ago. With that we could close this tracker.