-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go-ceph release tags #75
Comments
This was already discussed in #72. |
I dont see any mention of having release tags - only which package manager to use. This is tangential to the package management. |
I was referring to your |
Apologies, i meant to use it as an example for why release tags would be helpful. |
The initial "0.2" release is currently planned for 2020-02-11. |
https://github.com/ceph/go-ceph/releases/tag/v0.2.0 |
I would like to introduce the topic of having releases for go-ceph. This would also be related to #70 in the sense of dependency versioning.
For many this will act as a point of stability for CI/CD where pegged code releases can be used instead of relying on master branch. As good as a practice of writing tests for code, there is always the chance for new bugs to be introduced. Having release versions would help go-ceph users from introducing bugs that may be introduced via the master branch.
dep
(https://github.com/golang/dep) is one such tool that allows dependencies to be versioned to reduce the risk of introducing bugs into stable versions of go-ceph.The text was updated successfully, but these errors were encountered: