fix: update stability levels for different Kotlin components (#3905)

JetBrains · Nov 16, 2023 · 8a795c1 · 8a795c1
1 parent c0ff454
commit 8a795c1
Show file tree

Hide file tree

Showing 4 changed files with 3 additions and 11 deletions.
diff --git a/docs/topics/components-stability.md b/docs/topics/components-stability.md
@@ -62,7 +62,7 @@ We make sure to document precisely which subcomponents are not stable. We also d
 | **Component**                                         | **Status**   | **Status since version** | **Comment**                                                                       |
 |-------------------------------------------------------|--------------|--------------------------|-----------------------------------------------------------------------------------|
 | Kotlin/JVM                                            | Stable       | 1.0                      |                                                                                   |
-| Kotlin K2 (JVM)                                       | Alpha        | 1.7                      |                                                                                   |
+| Kotlin K2 (JVM, Native, Wasm, JS)                     | Beta         | 1.9.20                   |                                                                                   |
 | kotlin-stdlib (JVM)                                   | Stable       | 1.0                      |                                                                                   |
 | Coroutines                                            | Stable       | 1.3                      |                                                                                   |
 | kotlin-reflect (JVM)                                  | Beta         | 1.0                      |                                                                                   |

diff --git a/docs/topics/gradle/gradle-compilation-and-caches.md b/docs/topics/gradle/gradle-compilation-and-caches.md
@@ -280,8 +280,8 @@ When configuring the Kotlin daemon's JVM arguments, note that:
 
 ## The new Kotlin compiler
 
-The new Kotlin K2 compiler is in [Alpha](components-stability.md#stability-levels-explained).
-It has basic support for Kotlin JVM, JS, and Native projects.
+The new Kotlin K2 compiler is in [Beta](components-stability.md#stability-levels-explained).
+It has basic support for Kotlin JVM, Native, Wasm, and JS projects.
 
 The new compiler aims to speed up the development of new language features, unify all of the platforms Kotlin supports,
 bring performance improvements, and provide an API for compiler extensions.

diff --git a/docs/topics/multiplatform-mobile/multiplatform-mobile-introduce-your-team.md b/docs/topics/multiplatform-mobile/multiplatform-mobile-introduce-your-team.md
@@ -67,10 +67,6 @@ Also, in basic scenarios, you simply need to configure your project at the start
 
 When only the Android part of the team works with shared code, the iOS developers don't even need to learn Kotlin. But when you are ready for your team to move to the next stage, where everyone contributes to the shared code, making the transition won't take much time. The similarities between the syntax and functionality of Swift and Kotlin greatly reduce the work required to learn how to read and write shared Kotlin code. [Try it yourself!](https://play.kotlinlang.org/koans/overview)
 
-**Q: I heard that Kotlin Multiplatform is experimental technology. Does that mean that we shouldn't use it for production?**
-
-A: Experimental status means we and the whole Kotlin community are just trying out an idea, but if it doesn't work, it may be dropped anytime. However, after the release of Kotlin 1.4, **Kotlin Multiplatform is in Alpha** status. This means the Kotlin team is fully committed to working to improve and evolve this technology and will not suddenly drop it. However, before going Beta, there could be some migration issues yet. But even experimental status doesn't prevent a feature from being used successfully in production, as long as you understand all the risks. Check [the Kotlin evolution page](kotlin-evolution.md) for information about the stability statuses of Kotlin Multiplatform components.
-
 **Q: There are not enough multiplatform libraries to implement the business logic, it's much easier to find native alternatives.**
 
 A: Of course, we can't compare the number of multiplatform libraries with React Native, for example. But it took five years for React Native to expand their ecosystem to its current size. Kotlin Multiplatform is still young, but the ecosystem has tremendous potential as there are already a lot of modern libraries written in Kotlin that can be easily ported to multiplatform. 

diff --git a/docs/topics/multiplatform/multiplatform-dsl-reference.md b/docs/topics/multiplatform/multiplatform-dsl-reference.md
@@ -1,9 +1,5 @@
 [//]: # (title: Multiplatform Gradle DSL reference)
 
-> Multiplatform projects are in [Alpha](components-stability.md). Language features and tooling may change in future Kotlin versions.
->
-{type="note"}
-
 The Kotlin Multiplatform Gradle plugin is a tool for creating [Kotlin Multiplatform](multiplatform.md) projects.
 Here we provide a reference of its contents; use it as a reminder when writing Gradle build scripts
 for Kotlin Multiplatform projects. Learn the [concepts of Kotlin Multiplatform projects, how to create and configure them](multiplatform-get-started.md).