openshift / openshift/client-go
Future Release Branches Frozen For Merging | branch:release-4.23 branch:release-5.1 branch:release-5.2
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 120
- Forks
- 183
- PR merge metrics
- No merged PRs in 30d
Description
The following branches are being fast-forwarded from the current development branch (master) as placeholders for future releases. No merging is allowed into these release branches until they are unfrozen for production release.
release-4.23release-5.1release-5.2
For more information, see the branching documentation.
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
Start with the linked branching documentation to understand the release-branch policy. The issue names release-4.23, release-5.1, and release-5.2 as frozen placeholders, but it does not identify a file, test, or requested change; done is not defined beyond preserving the stated freeze.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100