Hi everyone! We are looking at providing a DI module for (Jetpack/JetBrains) Compose with <#C0BLU9K9...

# compose-desktop

[romainbsl]

Hi everyone!
We are looking at providing a DI module for (Jetpack/JetBrains) Compose with #kodein.
My question is simple: Does JetBrains Compose releases are following the Kotlin ones ?
Or the latency is as large as I should consider not including it in our main builds to avoid blocker ?

[olonho]

We generally try to follow Kotlin releases, but it takes some time to adjust compiler plugin for newly released Kotlin. cc: @jim

[jim]

Usually we merge the new Kotlin into the upstream Compose repository within 24 hours of the Kotlin release going public*.  Jetbrains Compose will then usually publish a release within a couple of days*.  Google will then usually publish a release on the wednesday following an alternating wednesday after the release (so no sooner than a week later, no later than three weeks later, two weeks on average)*.  So the short answer is that the latency for Desktop is usually a couple days and the latency for Google/Android is usually a couple weeks*.

* These dates do NOT constitute a commitment by Google nor Jetbrains; historical trends do not necessarily predict the future, workflows can change and unforeseen blocking bugs can happen, blah blah

[romainbsl]

Thank you for your clear answers 🙏 . This helps me think of how to manage our build process over new releases 🙂
Also, thanks a lot for all the great work around Compose!