{"action":"closed","issue":{"url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/580","repository_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs","labels_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/580/labels{/name}","comments_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/580/comments","events_url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/issues/580/events","html_url":"https://github.com/KhronosGroup/Vulkan-Docs/issues/580","id":263643684,"number":580,"title":"General stability of vk.xml, Release cycle","user":{"login":"Sharplifter","id":24571831,"avatar_url":"https://avatars3.githubusercontent.com/u/24571831?v=4","gravatar_id":"","url":"https://api.github.com/users/Sharplifter","html_url":"https://github.com/Sharplifter","followers_url":"https://api.github.com/users/Sharplifter/followers","following_url":"https://api.github.com/users/Sharplifter/following{/other_user}","gists_url":"https://api.github.com/users/Sharplifter/gists{/gist_id}","starred_url":"https://api.github.com/users/Sharplifter/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Sharplifter/subscriptions","organizations_url":"https://api.github.com/users/Sharplifter/orgs","repos_url":"https://api.github.com/users/Sharplifter/repos","events_url":"https://api.github.com/users/Sharplifter/events{/privacy}","received_events_url":"https://api.github.com/users/Sharplifter/received_events","type":"User","site_admin":false},"labels":[{"id":327326861,"url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/labels/Registry","name":"Registry","color":"d19fe3","default":false},{"id":324584797,"url":"https://api.github.com/repos/KhronosGroup/Vulkan-Docs/labels/wontfix","name":"wontfix","color":"ffffff","default":true}],"state":"closed","locked":false,"assignee":{"login":"oddhack","id":4693344,"avatar_url":"https://avatars1.githubusercontent.com/u/4693344?v=4","gravatar_id":"","url":"https://api.github.com/users/oddhack","html_url":"https://github.com/oddhack","followers_url":"https://api.github.com/users/oddhack/followers","following_url":"https://api.github.com/users/oddhack/following{/other_user}","gists_url":"https://api.github.com/users/oddhack/gists{/gist_id}","starred_url":"https://api.github.com/users/oddhack/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oddhack/subscriptions","organizations_url":"https://api.github.com/users/oddhack/orgs","repos_url":"https://api.github.com/users/oddhack/repos","events_url":"https://api.github.com/users/oddhack/events{/privacy}","received_events_url":"https://api.github.com/users/oddhack/received_events","type":"User","site_admin":false},"assignees":[{"login":"oddhack","id":4693344,"avatar_url":"https://avatars1.githubusercontent.com/u/4693344?v=4","gravatar_id":"","url":"https://api.github.com/users/oddhack","html_url":"https://github.com/oddhack","followers_url":"https://api.github.com/users/oddhack/followers","following_url":"https://api.github.com/users/oddhack/following{/other_user}","gists_url":"https://api.github.com/users/oddhack/gists{/gist_id}","starred_url":"https://api.github.com/users/oddhack/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oddhack/subscriptions","organizations_url":"https://api.github.com/users/oddhack/orgs","repos_url":"https://api.github.com/users/oddhack/repos","events_url":"https://api.github.com/users/oddhack/events{/privacy}","received_events_url":"https://api.github.com/users/oddhack/received_events","type":"User","site_admin":false}],"milestone":null,"comments":14,"created_at":"2017-10-07T14:04:56Z","updated_at":"2018-02-19T23:45:59Z","closed_at":"2018-02-19T23:45:59Z","author_association":"NONE","body":"Is there a special stable branch of the registry vk.xml? I thought things would not be released to [https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml](https://github.com/KhronosGroup/Vulkan-Docs/blob/1.0/src/spec/vk.xml) unless stability is basically guaranteed...\r\nI have often experienced strange behaviors with the copies of vk.xml put there.\r\nAs an example, take the 1.0.62 upgrade:\r\n\r\n>Change log for October 6, 2017 Vulkan 1.0.62 spec update: \r\n>\r\n>Other Issues:\r\n>\r\n> -  Fixed typo in flink:VkRenderPassSampleLocationsBeginInfoEXT (renamed\r\n>    field pname:pSubpassSampleLocations to\r\n>   pname:pPostSubpassSampleLocations).\r\n>\r\n>New Extensions:\r\n>\r\n> - Add +vk.xml+ entries for pending `VK_ANDROID_native_buffer` extension\r\n>    (note, this extension is not yet enabled).\r\n\r\nIt introduces breaking changes by renaming a field. Additionally I'm really unsure whether it's a good idea to introduce a structure referencing enum members defined in disabled extensions (meaning the value for `VkNativeBufferANDROID.sType`).\r\nFor the latter, I thought it might be possible to filter this out, but the whole concept of `<require...>` is either broken, too, or implicit to a grade that it will bring you to tears if you want to automate finding out which types and commands to actually take over. It's not like every required type and command actually has a `<require...>` reference...\r\nI also experienced experimental stuff getting renamed and thus \"moved\" to a non-exprimental stage. Which makes previously existing types and commands vanish that may have worked fine in an earlier revision of the spec.\r\nSo I'm totally confused about the rules of what can happen with the registry. I often find it is not really usable for code generation this way, even though it is of course helpful. Some revisions actually do work out, and since it is the only source of input for such activities, there's no real alternative.\r\nI think I've read some rants about code generation and vk.xml before, complaining about similar issues and certain other complexities.\r\nIs it possible we can improve things here? Is there a guide on rules?\r\n\r\n"}}
{"actor":{"display_login":"oddhack"}}