4.0.3 has been released
# kotests
sam
04/15/2020, 4:53 AM4.0.3 has been released
👍 2
s
Sebastian Schuberth
04/15/2020, 6:52 AMAre there any plans to, at some point, properly maintain https://github.com/kotest/kotest/blob/master/CHANGELOG.md and https://github.com/kotest/kotest/releases again?
s
sam
04/15/2020, 7:05 AMYes, the changelog is on my list to fix up this week
👍🏻 1
sam
04/15/2020, 5:34 PMThe changelog has been updated with 4.0.0, 4.01, 4.02 and 4.03
🎉 1
s
Sebastian Schuberth
04/15/2020, 6:32 PMGreat! Now the only thing I'm missing are the artifacts on Maven Central for 4.0.3 🙂
s
sam
04/15/2020, 6:32 PMthey're there
sam
04/15/2020, 6:32 PMs
Sebastian Schuberth
04/15/2020, 6:33 PMIndeed, interesting. I was looking at https://mvnrepository.com/artifact/io.kotest/kotest-core-jvm
s
sam
04/15/2020, 6:33 PMthat site is always so out of date
sam
04/15/2020, 6:33 PMI would recommend search.maven.org
s
Sebastian Schuberth
04/15/2020, 6:34 PMOk, I just like mvnrepository.com for its search across multiple repos.
s
sam
04/15/2020, 6:35 PMtrue
sam
04/15/2020, 6:35 PMand it has some nice graphs
sam
04/15/2020, 6:36 PMIt usually takes 24 hours to sync there, and about 30 minutes on search.maven.org
s
Sebastian Schuberth
04/15/2020, 6:36 PMGood to know.
s
sam
04/15/2020, 6:36 PMare you fully upgraded to kotest now ?
s
Sebastian Schuberth
04/15/2020, 6:39 PMs
sam
04/15/2020, 6:41 PMrelatively smooth ? For such a big change.
s
Sebastian Schuberth
04/15/2020, 6:43 PMYes, besides bulk search & replace of imports I only had to do very few more rounds of search & replace for imports that moved.
Sebastian Schuberth
04/15/2020, 6:44 PMAnd besides https://github.com/kotest/kotest/issues/1346, which was already fixed, I also didn't notice any behavior changes so far.
s
sam
04/15/2020, 6:44 PMIt was a one off big change kinda forced on us. I liked the old kotlintest name, and I was using it before kotlin.test existed!, but the small amount of confusion generated was a distraction.
s
Sebastian Schuberth
04/15/2020, 6:56 PMAh, I was wondering about the story behind that name change. So did Jetbrains approach you?
s
sam
04/15/2020, 6:58 PMNo I don't mean forced on us like that. My conversations with Jetbrains were that they were very happy with the project. I mean forced on us in the sense that there was some small degree of confusion, so it made sense for one project to change, and kotlin.test can't really change as jetbrains use the kotlin namespace.
sam
04/15/2020, 6:59 PMJetbrains have always been super supportive of the this project. For example, allowing us to use the K logo for the project even though it's derived from the actual kotlin logo
2 Views