Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Matching versions to rustls versions #393

Open
jsha opened this issue Mar 7, 2024 · 1 comment
Open

Matching versions to rustls versions #393

jsha opened this issue Mar 7, 2024 · 1 comment

Comments

@jsha
Copy link
Collaborator

jsha commented Mar 7, 2024

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 ?

@cpu
Copy link
Member

cpu commented Mar 11, 2024

Is the intent that we would match the most significant component only, but would release/version independently in the less significant components? E.g. a rustls-ffi 0.23.x release would be implied to be using Rustls 0.23.x, but we could release a rustls-ffi 0.23.1 for a bugfix that would be independent from a rustls 0.23.1?

In general I'm supportive of the idea and just want to make sure I understand the finer points w.r.t. what would happen if we need to publish additional rustls-ffi specific work after a breaking rustls update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants