:testballoon: :mega: Backwards compatibility requi...
# testballoon
o
testballoon 📣 Backwards compatibility requirements – your voice counts! As you may know, Sonatype plans to limit publications on Maven Central. Although nothing has been finalized yet, it makes sense to consider possible consolidation. TestBalloon has had backports up to Kotlin 2.0.0, which may not be needed in the long run. Which Kotlin versions do you require new TestBalloon releases to support (now or planned)? Multiple responses possible. 1️⃣ 2.4.0 2️⃣ 2.3.20 … 2.3.2 3️⃣ 2.3.0 … 2.3.1 4️⃣ 2.2.2 5️⃣ 2.2.0 … 2.2.2 6️⃣ 2.1.20 … 2.1.2 7️⃣ 2.1.0 … 2.1.1 8️⃣ 2.0.0 … 2.0.2
1️⃣ 17
2️⃣ 15
3️⃣ 5
4️⃣ 1
5️⃣ 1
6️⃣ 2
7️⃣ 1
8️⃣ 2
e
I voted and from my experience - current and previous would just be good for all my use cases - personal and client related. The urge by some dependency blocking other dependecy to upgrade is positive for me.
thank you color 1
d
I've recently migrated older microservices and the main problem is not being able to migrate some deps and others getting stuck because of them, I think minor version upgrades seemed to be easier though. One of them was a keycloak spi (keycloak is now based on quarkus and they bake in their own kotlin version... you litterally need to replace the stdlibs in the docker image to override them and hope nothing breaks --- and upgrading keycloak itself is risky db migrations and spi form changes...) As I migrate, as soon as I get to the first version test balloon supports, I tried migrating the tests to it. Cutting down on supported versions would make migration steps a bit bigger.