I'm fully in support of defined, rolling release trains. 6 months is a good start considering where they're coming from. I feel like that's still slightly too long though, and is one of the things I wish the Go team would change. The Go team's argument is that it takes time to fully test features before being able to release them, which I understand, but that's the whole point behind a multiple release train model.
But I digress. Faster Java & JVM updates will help Kotlin out as well moving forward. :)
But I digress. Faster Java & JVM updates will help Kotlin out as well moving forward. :)