No Release Tag Pushed since 4.1.0

[rohanKanojia]

Hi guys,

I'm from @fabric8io team. We maintain Kubernetes and Openshift Client which is used by a lot of people in the java ecosystem. We generate Kubernetes/Openshift model from go structs in api and origin. Right now our Openshift go struct model is pointing at v4.1.0[0], but I have noticed that no other tag has been pushed since then. Even Openshift 4.3.0 got released recently.

I'm just curious why Openshift upstream maintainers are not pushing tags. It's not like we're blocked as we can update model to latest master revision. But it would be nice if we upgrade with respect to Openshift releases.

[0] https://github.com/fabric8io/kubernetes-client#compatibility-matrix

[rohanKanojia]

@deads2k @smarterclayton @bparees @soltysh : polite ping, Would appreciate it if you could share your thoughts on this.

[soltysh]

It's still in-progress, there are several dependencies we need to handle before we'll be able to publish those.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[marun]

So long as this repo remains untagged, the workaround can be go get with the desired branch name (e.g. master, release-x.x) and go.mod will pin to the SHA of the branch head.

[rohanKanojia]

Yeah, we're managing with that till now. But we can't provide accurate compatibility matrices with respect to openshift versions

https://github.com/fabric8io/kubernetes-client#compatibility-matrix

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten /remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/api/issues/587#issuecomment-748599134): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[kaovilai]

How long does this repo plan to remain untagged? /reopen /lifecycle frozen

[openshift-ci[bot]]

@kaovilai: Reopened this issue.

In response to [this](https://github.com/openshift/api/issues/587#issuecomment-1554752560): >How long does this repo plan to remain untagged? >/reopen >/lifecycle frozen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.