Kotlin language release cycle
Kotlin can be used anywhere a Java virtual machine can be installed. But the thing does not stop there, there are variants of Kotlin that allow the language to be used in countless places, and its use in these areas is increasing.
Release cycle of Kotlin language
Kotlin releases are divided into three types: feature, incremental, and bug-correcting releases. However, these changes will only affect feature versions in most cases. Mainly we have the future releases, which will change language, and this will be done in a period of six months, although these can be postponed. Then we have the incremental releases, which cause improvements in terms of the tools of the system, this cycle varies between 2 to 3 months, between launches of characteristics. Finally, we have the bug fixes, which are done in a cycle of between one to two weeks, after an incremental release if corrections are needed.
KOTLIN will bring its new proposal with KOTLIN 1.7.0-BETA. Where will have several features and novelties:
- Changes in the compiler inference.
- The return of the min() and max() collection functions.
- Stabilization of definitely non-avoidable types.
- Updates for the new Kotlin/Native memory manager. Kotlin 1.7.0 will feature stable definitely non-voidable rates, which were introduced in Kotlin 1.6.20. These types have been added to provide better interoperability when extending generic Java classes and interfaces. Also, Kotlin 1.7.0-Beta includes more changes to the compiler inference. With this version, the compiler inference is automatically activated if a regular type inference cannot get enough information about a type without specifying the compiler option -Xenable-builder-inference