[fxbug.dev] Migrate bug numbers

This changes fxbug.dev/ URLs from Monorail bug numbers to the new
Fuchsia Issue Tracker numbers.

The migration to the new issue tracker was announced here:

Bug: 298074672
Change-Id: If622149a8ac326892d5d592a9b18e2af8821c2af
Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/Vulkan-Headers/+/980364
Fuchsia-Auto-Submit: Mitchell Kember <mkember@google.com>
Reviewed-by: Craig Stout <cstout@google.com>
1 file changed
tree: 67d55eb7ab0b92628e1a006dcd5dec91804349c1
  1. .github/
  2. .reuse/
  3. include/
  5. registry/
  6. scripts/
  7. tests/
  8. .gitattributes
  9. .gitignore
  10. BUILD.gn
  11. BUILD.md
  12. CMakeLists.txt
  13. CODE_OF_CONDUCT.adoc
  16. LICENSE.md
  17. OWNERS
  18. README.fuchsia
  19. README.md
  20. SECURITY.md


Vulkan header files and API registry

This repository contains Vulkan header files, include files for C and C++, and related scripts and tests.

Most of the files in this repository are sourced from, or generated from, other repositories as described in CONTRIBUTING.md. Vulkan-Headers exists as a staging area for these files, most of which are then consumed by downstream repositories used to build SDK components such as the Vulkan Validation Layers and Conformance Test Suite.

Developers normally obtain headers from the official Vulkan-SDK. They can also use headers from, or packaged from, this repository.

In most cases, developers should only need the headers, not the scripts and other material in this repository. In particular if you are packaging the headers for inclusion in Linux distributions or similar uses, we advise that you do not include the scripts, and direct potential users of the scripts to their canonical sources in the Vulkan Specification repository.




See BUILD.md

SDK Support

Vulkan-Headers are shipped as part of the official Vulkan-SDK

C/C++ Package Manager Support

Vulkan-Headers are also supported by both conan & vcpkg.

Version Tagging Scheme

Updates to this repository which correspond to a new Vulkan specification release are tagged using the following format: v<version> (e.g., v1.3.266).

Note: Marked version releases have undergone thorough testing but do not imply the same quality level as SDK tags. SDK tags follow the vulkan-sdk-<version>.<patch> format (e.g., vulkan-sdk-

This scheme was adopted following the 1.3.266 Vulkan specification release.