0.15 release planning
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 505
- Forks
- 157
- Avg merge
- 39m
- Merged PRs (30d)
- 1
Description
- #394
- #409
- #413
- #414
- #446
Maybe we should have some kind of extension trait to allow people to bring their own extensions?
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing issues #394, #409, #413, #414, and #446 to understand the planned 0.15 scope. Decide whether an extension trait for user-provided extensions belongs in that release and document the agreed design and work items; completion is a settled release plan rather than an identified code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100