Use a shared version number for all winit-* crates #4274
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are basically two ways we can do versioning of the
winit-*crates:There are many benefits to the first approach, including that we don't need to re-release unchanged crates for patch releases that only affect few crates, and that we might be able to re-use Winit crates between breaking changes of other crates (e.g. if
winit-corebecomes very stable).But the maintenance cost for us is also just quite high (there's a lot more combinations to test), and it makes it confusing for consumers to find the "mapping" between the main
winitcrate version and the platform-specific crate versions.We discussed it in our recent meeting, and came to the conclusion that we should go with a shared versioning scheme for simplicity for now, and only later have versions diverge if there's a concrete need.
Part of #3433.