You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the workgroup one area I’ve been focused on is the Swift Evolution Dashboard and the JSON file of evolution proposal metadata available at https://download.swift.org/swift-evolution/proposals.json.
I’m filing this issue because a GitHub search shows that this project references that URL.
I wanted to let you know that we are in the process of making some proposed changes to the schema and naming of the metadata file.
Thank you for the updates, James! In the hopes of being able to save you some work on keeping this thread up to date: This isn't a much used feature in our community chatbot (unfortunately), I'll get around to implementing the new endpoint at some point, but feel free to not continue updating this :)
Hi, I'm James Dempsey, a member of the Swift Website Workgroup.
As part of the workgroup one area I’ve been focused on is the Swift Evolution Dashboard and the JSON file of evolution proposal metadata available at
https://download.swift.org/swift-evolution/proposals.json
.I’m filing this issue because a GitHub search shows that this project references that URL.
I wanted to let you know that we are in the process of making some proposed changes to the schema and naming of the metadata file.
The proposed modifications are in the Swift Forums post at https://forums.swift.org/t/swift-evolution-metadata-proposed-changes/70779.
Please feel free to provide any feedback in that thread.
That post also describes the transition plan to migrate to the new metadata schema.
During the transition period, the
proposal.json
file will continue to be available at its current URL with its current schema.A file with the new schema will also be available during the transition period.
For full details and to provide any feedback you may have, please review the post in the Swift forums.
The text was updated successfully, but these errors were encountered: