-
Notifications
You must be signed in to change notification settings - Fork 474
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use correct start page for features component and fix some cross-modu…
…le xrefs
- Loading branch information
Showing
3 changed files
with
19 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,14 +1,17 @@ | ||
// Copyright 2022-2024 The Khronos Group Inc. | ||
// SPDX-License-Identifier: CC-BY-4.0 | ||
|
||
= Vulkan Roadmap and Feature Descriptions | ||
= Vulkan Feature Descriptions | ||
|
||
This component includes the Vulkan Roadmap, the Vulkan 2022 Profile Roadmap, | ||
and all published extension feature descriptions. | ||
This component includes all published extension feature descriptions, as | ||
well as the original rationale for the xref:proposals/Roadmap.adoc[Vulkan | ||
Roadmap] process which resulted in the | ||
xref:spec::appendices/roadmap.adoc[Roadmap 2022 and Roadmap 2024] milestones. | ||
|
||
When a Vulkan extension is initially proposed, a feature description is | ||
written outlining the proposed API, from which specification language is | ||
written. | ||
Once the extension is published, the initial "proposal", now | ||
referred to as a "feature description", is retained to act as | ||
supplementary documentation on that extension. | ||
When a Vulkan extension begins development, a "`proposal`" document is | ||
written outlining the proposed API. | ||
The proposal is the basis from which specification language is written. | ||
|
||
When the extension is published, the proposal - now referred to as a | ||
"`feature description`" - is retained to act as supplementary documentation | ||
on that extension. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters