openshift / openshift/hypershift
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
- Go
- Stars
- 541
- Forks
- 567
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 136
Description
The following branches are being fast-forwarded from the current development branch (main) 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
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 branching documentation linked in the issue and review the listed release branches. No source file, test, or entry point is named, and the issue provides no implementation task or completion criteria beyond keeping these branches unavailable for merging until they are unfrozen.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100