Stability of Kotlin components

Here's a quick guide to these stability levels and their meaning:

Experimental means "try it only in toy projects":

• We are just trying out an idea and want some users to play with it and give feedback. If it doesn't work out, we may drop it any minute.

Alpha means "use at your own risk, expect migration issues":

• We intend to productize this idea, but it hasn't reached its final shape yet.

Beta means "you can use it, we'll do our best to minimize migration issues for you":

• It's almost done, user feedback is especially important now.

• Still, it's not 100% finished, so changes are possible (including ones based on your own feedback).

• Watch for deprecation warnings in advance for the best update experience.

We collectively refer to Experimental, Alpha and Beta as pre-stable levels.

Stable means "use it even in most conservative scenarios":

• It's done. We will be evolving it according to our strict backward compatibility rules.

Please note that stability levels do not say anything about how soon a component will be released as Stable. Similarly, they do not indicate how much a component will be changed before release. They only say how fast a component is changing and how much risk of update issues users are running.

The Kotlin GitHub organization hosts different Kotlin-related projects. Some of them we develop full-time, while others are side projects.

Each Kotlin project has two GitHub badges describing its stability and support status:

• Stability status. This shows how quickly each project is evolving and how much risk the users are taking when adopting it. The stability status completely coincides with the stability level of the Kotlin language features and its components:

  • stands for Experimental

  • stands for Alpha

  • stands for Beta

  • stands for Stable

• Support status. This shows our commitment to maintaining a project and helping users to solve their problems. The level of support is unified for all JetBrains products.
  See the JetBrains Open Source document for details.

A stable component may have an experimental subcomponent, for example:

• a stable compiler may have an experimental feature;

• a stable API may include experimental classes or functions;

• a stable command-line tool may have experimental options.

We make sure to document precisely which subcomponents are not Stable. We also do our best to warn users where possible and ask to opt them in explicitly to avoid the accidental use of features that have not been released as stable.

note

By default, all new components have Experimental status.

For language features and new design proposals, see Kotlin language features and proposals.