No Release Tag Pushed since 4.1.0
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 121
- Forks
- 890
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 22
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named; start by reviewing the repository's release and tagging process and the tags following v4.1.0. Done would be a maintainer-confirmed explanation or release-aligned tags for newer OpenShift versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100