Add subversioning info for WASI 0.2 #43
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adresses #30 and the recent release of WASI 0.2.2. It adds a new subsection listing the WASI 0.2 subreleases and details the changes.
I am aware that this is not perfect, and I suppose that each WASI proposal will be able to evolve on its own (and managing its own versions) by the time they reach phase 5. For the time being though it should be a good enough solution to keep the website up to date with the latest WASI changes.
If the people managing the WASI 0.2 releases have a documentation somewhere detailing the steps to follow, adding the update of this website to the list could also be a good idea.