[Docs] Update ROADMAP.md (May/2024). #3382
Conversation
|
Hello, I am a code review bot on flows.network. Here are my reviews of code commits in this PR. |
github-actions
bot
added
the
documentation
|
I think we should add LLM-related features in the roadmap.
|
|
Hi @q82419 Are there any updates on the ROADMA.md? We should also add what we have done since 2024 on the roadmap.md. |
docs/ROADMAP.md
Outdated
| | Proposal | WASM C API proposal | Q4 / 2024 | | ||
| | Proposal | WASM memory64 proposal | Q4 / 2024 | | ||
| | Feature | DWARF symbol | Q4 / 2024 | | ||
| | Proposal | Component model proposal | ?? / 2024 | |
docs/ROADMAP.md
Outdated
| 2. Any individual can request inclusion in the roadmap by commenting on the issue and volunteering as an assignee. | ||
| 3. WasmEdge maintainers will collect the proposed roadmap entries along with their respective timelines and assignees, then update them within the issue. | ||
| 4. Existing roadmap entries which not reach their deadlines will be retained in the new quarter. | ||
| 5. Roadmap entries that have reached their deadlines will be marked as completed or dropped, and the associated issues will be closed. |
There was a problem hiding this comment.
Complete, drop, or update deadline? Since maybe the entry is delayed by accident.
There was a problem hiding this comment.
We should figure out if there is any GitHub-Bot that can help to auto-close the stale proposals.
There was a problem hiding this comment.
Sure, I think the deadline can be updated due to some reason. This can be discussed in the new quarter roadmap.
There was a problem hiding this comment.
The timeslot is based on quarters now. How about:
- Propose a quarter -> Stale
- Propose two quarters -> Close
It should be fine to drop a proposal if we have no plan to implement it in half a year.
Signed-off-by: YiYing He <yiying@secondstate.io>
No description provided.