Matching versions to rustls versions

Open
  • Is something wrong?
#393 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
cryptography

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.

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 ?

Dominant language
Rust
Stars
171
Forks
45
Avg merge
16h 43m
Merged PRs (30d)
18

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rustls/rustls-ffi

All issues in rustls/rustls-ffi

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.