Query on project release tags

[Bharath B]

Hi All,

Recently [1], [2] and [3] PRs got merged in `gcp-compute-persistent-disk-csi-driver` and `gcp-filestore-csi-driver` projects and I had a query on when these commits will be part of a release tag.

PR [3] which was merged on April 15th was not part of the recent tag created for v1.6.15 release, which had a commit merged on April 20th.

I was wondering do we need create any request for including the commits in a release and to get release tag created. Does releases follow any timeline or could we make a quick request for a release tag.

Thanks in advance,

Bharath B

[1] - https://github.com/kubernetes-sigs/gcp-compute-persistent-disk-csi-driver/pull/1377

[2] - https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/pull/630

[3] - https://github.com/kubernetes-sigs/gcp-filestore-csi-driver/pull/640

[Saad Ali]

@Matthew Cary can you help with Bharath's question?

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-storage" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-st...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-storage/4718e367-e46c-464c-9de4-fc19c60c9107n%40googlegroups.com.

[Matthew Cary]

Hi Bharath,

v1.6.15 was created from the release-1.6 branch, it looks like [3] was submitted to master. We have the same model as k8s, where new changes to master aren't released until a new minor (ie, 1.7) is cut.

We cut a new minor when there are "significant" changes, which is admittedly subjective and hard to predict.

If your PRs are for minor features, then the easiest thing to do would be to backport them to the most recent minor. You can use github's automatic cherry-pick, by putting /cherry-pick release-1.6 in to the comment thread on your merged PR. That will automatically create the backport PR which is approved in the normal process. Then it will get in the next patch release which should be a few weeks (as there probably will be CVEs to fix).

I'm not sure offhand of the scope of your features and if they're appropriate to backport, I'd reach out to whoever approved your PRs.

[Bharath B]

Hi Matthew,

Thank you so much for the detailed response.

Regards,

Bharath B