Closed onlyjob closed 5 years ago
We don't have a plan to do so at this time. liblxc itself is versioned but go-lxc is made to work with all stable versions of liblxc and so doesn't need to follow its versioning.
Major API breaks do lead to version bumps on go-lxc though, as can be seen by the current version being v2.
This is so projects depending on this library (e.g. nomad-driver-lxc) could refer to it by proper release version. Not every commit is compatible and API breakage already happened here.
Most of the Go pinning tools work with hashes, so you can always pin on what you've last tested.
Please consider tagging formal semantic releases.
Thanks.