kubernetes-sigs / kubernetes-sigs/gateway-api
GEP: Rename Core and Extended support levels
- Dominant language
- Go
- Stars
- 3k
- Forks
- 789
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 45
Description
**What would you like to be added**:
This GEP proposes that we rename Core and Extended support levels to Required and Optional, in the interest of increasing clarity and preventing confusion.
**Why this is needed**:
We already see confusion in talking about Core and Extended (particularly confusing Extended with Experimental), and we almost always use Required and Optional to explain the terms. So we should just rename.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating all references to the Core and Extended support levels in the Gateway API repository and review the existing GEP terminology. Done means the support levels are consistently renamed to Required and Optional without confusing them with Experimental.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100