RustCrypto / RustCrypto/rustls-rustcrypto
Release 0.23.0 Tracker
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 130
- Forks
- 21
- Avg merge
- 18h 6m
- Merged PRs (30d)
- 1
Description
What should we add to the initial release ?
TL;DR "it's tested sane" a.k.a "it builds, it tests, it benches, it's no_std, it's crypto is sane" ?
Release 0.23.0 train
- #30
- #31
- via #48
- #33
- Concensus: Minor version in sync (re-open if issue needs re-visiting)
- #34
- via #43
- #36
- #38
- #41
- re-directed #56
- #44
- Consensus: due to lock-step with rustls we cannot control MSRV upgrades
- #49
- #50
- #52
- #53 (all doc issues wrapped into this)
need to raise some more issues me thinks
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
Review the Release 0.23.0 checklist and the unresolved linked issues, especially #30, #49, #50, and #52. The tracker does not identify a file, test, or single change, and completion would require resolving the remaining release criteria and updating the checklist.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100