Versioning? about checkpointctl HOT 5 CLOSED

There is no version, yet, because I didn't want to commit to an API. To not have to deal with GO's requirements when it comes to package versioning, I just left it without.

We are using it in CRI-O and Podman and to be able to easily change the API there is no version.

We can add something like 0.1.0 if it would help you. Once the API seems settled there will be a version.

from checkpointctl.

There is no version, yet, because I didn't want to commit to an API. To not have to deal with GO's requirements when it comes to package versioning, I just left it without.

We are using it in CRI-O and Podman and to be able to easily change the API there is no version.

Make sense, ty for the explanation :)

We can add something like 0.1.0 if it would help you. Once the API seems settled there will be a version.

No it's better like this otherwise the package will remain not-updated until the api. I'm going to create a git package and once a versioning will become a thing here I will create another package that will follow the versioning.

Thanks!

from checkpointctl.

fyi: this is the package: https://aur.archlinux.org/packages/checkpointctl-git

from checkpointctl.

We just tagged a v0.1.0 release.

from checkpointctl.

Great! will create another package :)

from checkpointctl.