Create initial release of csi-driver-iscsi

[saad-ali]

1. Do some manual testing to ensure the driver works as intended.
2. Create a release-0.1 branch for kubernetes-csi/csi-driver-iscsi
3. Cut an official release v0.1.0 release of this driver from the new branch.
4. Push a csi-driver-iscsi:v0.1.0 container (either to quay or gcr.io whatever the Kubernetes CSI team decides)

[saad-ali]

CC @msau42 @prateekpandey14

[msau42]

Before we do that, we should also:

• Use release-tools for common process
• Remove dependency on csi-lib-common

cc @pohly

[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.

[saad-ali]

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.

[pohly]

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.

[msau42]

cc @j-griffith

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[msau42]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[msau42]

/lifecycle frozen