After having migrated the build to use the new system Volkan put together for the main repo, I’ve managed to get the build there working in a similar streamlined fashion. Thus, it’ll be a lot easier to cut some releases there, and wow do we have a backlog of them to get through! So here’s what I’m proposing for releases:
* 1.3.0 - next release. This includes a few API updates, cleaned up website, dependency updates, etc. 1.3.x will be the last version to support Kotlin 1.3 (for context, Kotlin is at version 1.8.10 at the moment). * 1.4.0 - This release will bump the Kotlin version requirement to 1.4.x. While backward compatibility seems to stretch back to 1.3.x., this does make it harder to use as a dependency since we need to use a provided-scope dependency to avoid using the wrong Kotlin version in an application. Thus, this will be the start of some catch-up releases to pull the baseline Kotlin version required up to a more reasonably modern version. Amusingly enough, these version numbers coincide with Kotlin itself, so it’s possible to make 1.5.0 require Kotlin 1.5, 1.6.0 require Kotlin 1.6, and so forth. * 1.5.0 - Kotlin 1.5 * 1.6.0 - Kotlin 1.6 etc. The 1.3.0 and 1.4.0 releases are the more immediately relevant ones (as in I’d like to do them in a couple weeks). Since Spinnaker has been stuck on Kotlin 1.4 for a while, I didn’t exactly have a pressing need to move toward the bleeding edge, but even that project is working through dependency updates which will eventually get to Java and Kotlin upgrades, so I’d also like to release some later versions before then as well. Anything else desired for these releases? The Kotlin releases/roadmap are on https://kotlinlang.org/docs/releases.html which may help discover any new APIs or features that would be relevant to support or use.
