Consider supporting all official K/N targets

[qwwdfsad]

In kotlinx.* libraries we finally publish artifacts for all officially-supported targets. To mitigate potential questions about various implementations aspects (including the level of support in tooling, overall quality level and regular testing), we refer to official recommendations.

It would be nice if Okio could do the same in order to make the overall targets support across the libraries more consistent (i.e. will enable other libraries [that depend on Okio] to support lower-tier targets); in particular, we've already encountered it in our kotlinx-serialization-okio integration: https://github.com/Kotlin/kotlinx.serialization/blob/79076e26ef860967688403d27cd8313d8bf9ba66/gradle/native-targets.gradle#L111

[JakeWharton]

I believe we're blocked on the integration and release of the new targets in kotlinx.datetime first. Once that happens we can update and add the targets here.

[Laxystem]

I've created an issue on KotlinX.DateTime for LinuxArm64, a tier 2 support platform: Kotlin/kotlinx-datetime#300

[Laxystem]

KotlinX DateTime 0.4.1 was released, with LinuxArm64 support. Any news from Okio?
Kotlin/kotlinx-datetime#300

[JakeWharton]

#1301

[bcmedeiros]

Is there any platform missing? Is there a release planned?

[swankjesse]

LinuxArm64 is available in Okio 3.6.0.

[sandwwraith]

What about Tier 3 targets? We have them in the serialization but not in the datetime yet. Do you plan to add them?

[swankjesse]

@sandwwraith Lets do it.

[sandwwraith]

I've created Kotlin/kotlinx-datetime#311 for that. It turns out there are some problems with timezone DBs that prevent them from being added to kotlinx-datetime.

[BenWoodworth]

It looks like kotlinx-datetime has the android targets now in v0.6.0. Does that mean we're unblocked?

[swankjesse]

@BenWoodworth oooh yep!