Skip to content

Conversation

@madsmtm
Copy link
Member

@madsmtm madsmtm commented Jun 7, 2025

There are basically two ways we can do versioning of the winit-* crates:

  1. Distinct versioning for each crate.
  2. A single shared version for all the 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-core becomes 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 winit crate 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.

@madsmtm madsmtm requested review from jackpot51 and notgull as code owners June 7, 2025 13:22
@madsmtm madsmtm added the S - meta Project governance label Jun 7, 2025
@madsmtm madsmtm added the S - maintenance Repaying technical debt label Jun 7, 2025
@madsmtm madsmtm removed request for jackpot51 and notgull June 7, 2025 14:53
@kchibisov kchibisov merged commit e1bccb6 into master Jun 8, 2025
57 checks passed
@kchibisov kchibisov deleted the madsmtm/shared-versioning branch June 8, 2025 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S - maintenance Repaying technical debt S - meta Project governance

Development

Successfully merging this pull request may close these issues.

3 participants