Update versioning docs to reflect recent changes in the release process. #4308
+61
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
release-note
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bexxmodd The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
size/M
Contributor
Author
|
/cc @kflynn |
k8s-ci-robot
added
the
cncf-cla: yes
youngnick
reviewed
Dec 5, 2025
Comment on lines
+17
to
+27
| To get a new item into the Experimental channel, you need: | ||
| * A Who/What/Why [GEP](../geps/overview.md) merged as Provisional | ||
| * Implementations willing to sponsor the item by agreeing to implement it as an | ||
| experimental feature | ||
| * Items affecting north-south aspects of Gateway API require three sponsors | ||
| * Items affecting only east-west aspects require two sponsors | ||
|
|
||
| The GEP can be merged into Provisional before soliciting sponsors. Once an item | ||
| moves from Provisional to Implementable, it will be automatically dropped if it | ||
| doesn't make any significant progress in six months. This process is handled | ||
| with a public review, typically at the first meeting of every month. |
Contributor
There was a problem hiding this comment.
I'm worried that this will go stale - any chance we could put something like "There are requirements for each level change, and those are documented at ". That way, if we update the GEP overview doc with the process, we don't need to update it here as well.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/kind documentation
What this PR does / why we need it:
Update versioning docs to reflect recent changes in the release process.
Which issue(s) this PR fixes:
Fixes #4282
Does this PR introduce a user-facing change?: