v1.4.0 Release-Cycle: GEP Iteration and Review #3824
Pinned
shaneutt
announced in
Announcements
Replies: 2 comments 2 replies
-
Could you provide more context on this note for #91?
|
Beta Was this translation helpful? Give feedback.
2 replies
-
Note: we have moved forward the timeline to have |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The scoping phase for standard and experimental channels for v1.4.0 has concluded.
The following standard features are accepted for the release:
As for experimental, we currently have capacity for 4 regular issues, and 2 issues that support the transition from ingress to Gateway API based on the current experimental pipeline. These experimental features are accepted:
Normal Pipeline (max 4):
Ingress Pipeline (max 2):
The following timeline shows the expectations for the experimental feature transitions:
June 10GEP PR with "What?"/"Why?"/"Who?" is ready for review✔️June 17GEP PR with "What?"/"Why?"/"Who?" is merged✔️July 1GEP PR with proposed API details (the "How?") is ready for reviewheavy_check_mark:After this, then final implementations will be be due in time for code freeze on August 26th. See the milestone for more details after the GEP iterations and review cycle.
The timeline for standard features will be done a little different and communicated uniquely for each issue. Expect updates and check-ins on each individual feature during this phase, and if you have any questions, concerns or need support please reach out!
Beta Was this translation helpful? Give feedback.
All reactions