aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJuan Ramos <juan@lunarg.com>2023-10-04 16:56:58 -0600
committerJuan Ramos <114601453+juan-lunarg@users.noreply.github.com>2023-10-04 21:04:04 -0600
commit0067d4cb64dad8e8c753efcf1dd120347e682300 (patch)
tree83b2db9182e6fe1d906bf2d70302f0513cfd6b26
parente483d0dfc7b33483cefd80632d141fe0bacdfb9a (diff)
downloadusermoji-0067d4cb64dad8e8c753efcf1dd120347e682300.tar.xz
docs: New SDK branch convention
Next SDK we will be changing branch/tag naming scheme from sdk-1.x.yyy to vulkan-sdk-1.x.yyy
-rw-r--r--README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md
index f9726955..0196b88c 100644
--- a/README.md
+++ b/README.md
@@ -25,11 +25,11 @@ Please see the [GOVERNANCE.md](GOVERNANCE.md) file in this repository for reposi
## Version Tagging Scheme
-Updates to the `Vulkan-Tools` repository which correspond to a new Vulkan specification release are tagged using the following format: `v<`_`version`_`>` (e.g., `v1.1.96`).
+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 `sdk-<`_`version`_`>.<`_`patch`_`>` format (e.g., `sdk-1.1.92.0`).
+**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-1.3.266.0`).
-This scheme was adopted following the 1.1.96 Vulkan specification release.
+This scheme was adopted following the `1.3.266` Vulkan specification release.
## License
This work is released as open source under a Apache-style license from Khronos including a Khronos copyright.