Create initial release of csi-driver-nfs about csi-driver-nfs HOT 21 CLOSED

Before we do that, we should also:

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

cc @pohly

from csi-driver-nfs.

@wozniakjan one more issue I think should be done for the release: #25

from csi-driver-nfs.

A 2.0.0 has been released! Thanks @wozniakjan for all the work in finishing up all the last mile tasks!

/close

from csi-driver-nfs.

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.

from csi-driver-nfs.

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

from csi-driver-nfs.

/remove-lifecycle stale

from csi-driver-nfs.

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

from csi-driver-nfs.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

from csi-driver-nfs.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

from csi-driver-nfs.

@fejta-bot: Closing this issue.

from csi-driver-nfs.

/reopen
/lifecycle frozen
/help

from csi-driver-nfs.

@msau42: Reopened this issue.

from csi-driver-nfs.

In order to use csi-release-tools, we also need to switch to go mod too.
/help

from csi-driver-nfs.

@msau42:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

from csi-driver-nfs.

I can try to convert this to go modules over the weekend unless anyone else wants to take that sooner

from csi-driver-nfs.

@msau42 do you have any more steps in mind before the v1.0.0 release? Btw. I think the tag of the first release should actually be v1.0.0 with major 1 instead of here proposed v0.1.0 with major 0. Given major 1 is in the manifests to pull the docker image and also in code that registers the plugin.

I am afraid my account isn't authorized to create the release itself so it may need to be you to perform the final steps.

from csi-driver-nfs.

Can we also address these two issues?
#19
#3

from csi-driver-nfs.

I will look into making sure travis and prow are setup on this repo

from csi-driver-nfs.

Can we also address these two issues?
#19
#3

sure thing, will do so by Monday

from csi-driver-nfs.

Also I just enabled prow pull jobs on this repo, and double checked travis and quay are setup to build and release images.

from csi-driver-nfs.

@msau42: Closing this issue.

from csi-driver-nfs.