-
Notifications
You must be signed in to change notification settings - Fork 63
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
Create initial release of csi-driver-iscsi #4
Comments
Before we do that, we should also:
cc @pohly |
I was about to suggest the same as @msau42. One comment about branching: it is not necessary to start such a branch right away. The initial release can also be done from the master branch and then (if necessary) a maintenance branch can be created later. |
Sure. As long as we cut a branch before the next release. I want to make sure that we never end up with a situation where an older release does not have a branch that we can go back to and make patch fixes. |
I just don't understand what you are worried about here. What would prevent creating that branch at a later time, when it is needed? We can have v1.1.0, v1.2.0, v1.3.0 all tagged on master, with no branches. When we decide that we need a v1.1.1 with a certain bug fix from master, we create a release-1.1 branch off v1.1.0 and backport that fix. Then v1.1.1 is tagged on that branch. |
build.make: fix pushing of "canary" image from master branch
cc @j-griffith |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/lifecycle frozen |
/assign @humblec |
We now have v0.1.0 here https://github.com/kubernetes-csi/csi-driver-iscsi/releases/tag/v0.1.0 , once we have e2e in place we will be releasing v1.0.0 |
v1.0.0 is for GA release, once we have e2e test, we could claim it's beta release with v0.2.0 |
release-0.1
branch for kubernetes-csi/csi-driver-iscsiThe text was updated successfully, but these errors were encountered: