openshift / openshift/ingress-node-firewall
Future Release Branches Frozen For Merging | branch:release-4.23 branch:release-5.1 branch:release-5.2
Open
Nobody has claimed this yet.
tide/merge-blocker
- Dominant language
- C
- Stars
- 77
- Forks
- 46
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 13
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
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
Read the issue body and follow the linked branching documentation to understand the freeze policy for release-4.23, release-5.1, and release-5.2. No code or documentation change is requested; the issue is complete when the branch freeze status is understood or the release process provides a specific follow-up.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100