WebAssembly / WebAssembly/WASI
Versioning/Tagging?
Open
Nobody has claimed this yet.
P-http
S-inactive
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
With the wasi-http spec continuing to iterate, does it make sense to tag specific versions so that guests/hosts can align on what to expect?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue discusses versioning and tagging for the wasi-http specification but names no files, tests, or entry points. Start by reviewing the current wasi-http specification and its release process, then determine the versioning requirements and agreement needed before implementation can be considered complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- api, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100