With Bintray sunsetting I'm going to move KVision ...

# kvision

[Robert Jaros]

With Bintray sunsetting I'm going to move KVision to Maven Central. It's probably a good moment to consider renaming maven group name from "pl.treksoft" to "io.kvision". What do you think?

[Big Chungus]

yes please!

[Robert Jaros]

Do you think it would be a breaking change? 🙂 I don't want KVision 4.x ...

[Big Chungus]

Well, i think repoMigraion is already breaking enough. And changing import pl.treksoft.* to import io.kvision can be done via IDE in one go.

[Big Chungus]

You won't get another chance like this 😄

[Big Chungus]

Plus I see no harm in kvision 4.*.

[Robert Jaros]

Hmm ... thinking this way Bootstrap 5 will come with KVision 5 😉

[Big Chungus]

Right! Yeah, I think it'd make sense to skip v4 even and just sync kvision major with bootstrap

[Big Chungus]

Or if bootstrap5 will not come out before jcenter dies, use v4 as a placeholder for repo migration

[Robert Jaros]

Perhaps you are right, I will go with 1.4.30 and IR being default as well, so 4.x is probably justified.

[Robert Jaros]

I think it will take some time to support BS 5 after it will be released.

[Robert Jaros]

So right now it's a long way till KVision 5 😉

[Robert Jaros]

And publishing to Maven Central is a lot more complicated than Bintray. Apparently I need to watch a dozen of videos (!) to learn this! 😬

[Big Chungus]

I wish there'd be a guide somewhere on how to publish MPP lib to central...

[Robert Jaros]

redux-kotlin is published to central, at least I can take a look at the configuration

[jschneider]

If you want to rename, you should rename now.

But I would really consider a new major version number. Changing packages in a minor release it at least "surprising"