Matching versions to rustls versions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 170
- Forks
- 43
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 10
Description
When rustls-ffi started, it was producing incompatible API changes in the C API at a faster rate than rustls itself, so I chose an independent versioning scheme. Now the rate of API changes in rustls has picked up, and the rate of API changes in rustls-ffi has slowed down, so it makes more sense to give them the same versioning scheme. So for instance, the next release of rustls-ffi would be 0.23.1, and it would build against rustls 0.23.1. WDYT @cpu ?
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
Start by reviewing the current rustls-ffi and rustls release and versioning arrangements; the issue names no files or tests. Define the version mapping and release changes, then confirm that the next release and its rustls dependency use the agreed matching versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cryptography
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100