Is there a roadmap to 1.0? Looking at the project...

# kotlinx-datetime

[CLOVIS]

Is there a roadmap to 1.0?

Looking at the project activity, I don't see any major changes being planned

[jw]

The pluggable tzdb is a pretty major change that's happening

[Dmitry Khalanskiy [JB]]

The roadmap is:

• Adding explicit time gap/time overlap handlers github.com/Kotlin/kotlinx-datetime/pull/626 is a breaking change. It's already in the main branch, but not yet published.
• Like Jake said, explicit timezone databases github.com/Kotlin/kotlinx-datetime/pull/610 are a major upcoming change.
• The TimeZone class hierarchy needs to be remade. In its current form, its conceptual model is arbitrary, and it doesn't support writing custom TimeZone instances.
• In parallel to that, calendar-based arithmetic operations are under review. We are considering introducing an API similar in spirit to java.time.ZonedDateTime, to mitigate the need to pass a TimeZone everywhere.
---
• After the tasks above are finished, there are no major breaking changes blocking us from publishing 1.0!
---
• Localized datetime formatting is crucially important, but luckily, it doesn't require breaking any existing APIs, so we're prioritizing stabilization over it.

[CLOVIS]

For context, I'm writing serializers for MongoDB, and so of course I need to serialize local datetime types. However I still see many projects on KotlinX.Datetime 0.6.0 because of the Instant and Clock migration, so I do worry a bit of another such breaking change in the future

[CLOVIS]

I think the tzdb change will have virtually no impact on 99% of projects, no?

[Dmitry Khalanskiy [JB]]

It deprecates TimeZone.of, TimeZone.availableZoneIds, and TimeZone.currentSystemDefault, so I'd expect much more than 1% of all projects to be affected!

[CLOVIS]

Oh 😅