Kover since 0.8.0 is marked as "0.8.0-beta". To cl...

# code-coverage

[CLOVIS]

Kover since 0.8.0 is marked as "0.8.0-beta". To clarify, is Kover 0.8.0-beta "more beta" than 0.7.0, or is it just that the naming scheme has changed and all pre-1.0.0 releases are now marked with -beta?

[Chrimaeon]

I guess you infer by the 0.x.y that it is a beta version? I think you’re mixing up 2 things - Stable API’s and “well tested release”. So 0.7.0 was not a beta version because is was well tested to not have errors and obvious bugs. 0.8.0-beta might contain such issues.

https://semver.org/#spec-item-4

And it’s not 1.0.0 because there was never a stable API released.

[CLOVIS]

I know, but JetBrains doesn't follow SemVer. For example, you'll see that 2.0.0-RC1 isn't valid (2.0.0-RC.1 would be correct).

Also, notice how Dokka versions until 1.4.0-RC had no qualifier, then from 1.4.0 to 1.5.31 they were called "Alpha" even though the stability level didn't change, then they stopped being called "Alpha" in 1.6.0 at which point the stability level did change, since Dokka is now stable (to my knowledge).

So, it's unclear to me whether Kover 0.8.0-beta is "a beta for a future version that will be called 0.8.0" (which would be SemVer-compliant) or just how they name all versions now, like they did for Dokka.

[Chrimaeon]

since it’s marked it’s “Pre-Release” I guess it’s likely what I said.

[Chrimaeon]

also this for the 1st beta “release”

[Javier]

Agree with jetbrains not following semver in Kotlin (not sure rest of libraries)

But RC1 or RC.1 is matter of taste, both fulfill semver specifications