-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement job allocation completions index enhancement #1073
Comments
/stage alpha Hi @fudali113, I'm the 1.16 Enhancement Lead. I've added this to the 1.16 Tracking Spreadsheet. Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly. As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements. Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29. |
@lachie83 @justaugustus can we get a label added for sig/job? is that a SIG? I'm not familiar with that one. |
@kacole2 |
@fudali113 this is a reminder that Enhancement Freeze is tomorrow and this keep needs to be merged by EOD. If not, it will be removed from the milestone. Thanks |
Enhancement Freeze has passed for 1.16. The KEP at #1072 was never merged and now this is being removed from the 1.16 milestone. If this would like to be re-added, please file an exception and it will require approval from the release lead. /milestone clear |
Hey there @fudali113 -- 1.17 Enhancements lead here. I wanted to check in and see if you think this Enhancement will be graduating to alpha/beta/stable in 1.17? Just a reminder that for it to be accepted -- the KEP must be merged, in an implementable state and have both a test plan and graduation criteria defined before the Enhancement Freeze. The current release schedule is:
If you do, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍 Thanks! |
Hey there @fudali113, 1.17 enhancements team checking in again 👋. We're quickly approaching the enhancements freeze (EOD PT, October 15th). As a reminder, your KEP needs to be merged by Oct 15th to make it into the 1.17 release, with the following criteria satisfied:
|
@fudali113 -- Unfortunately the deadline for the 1.17 Enhancement freeze has passed and the KEP still isn't merged. For now this is being removed from the milestone and 1.17 tracking sheet. If there is a need to get this in, please file an enhancement exception. /milestone clear |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Hey there @fudali113 -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18? The current release schedule is: Monday, January 6th - Release Cycle Begins To be included in the release, this enhancement must have a merged KEP in the If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍 We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements |
@johnbelamaric I don't think any work will happen for 1.18 here. |
sorry,i just saw this comment now;so i miss this Enhancement alpha in 1.18 ; What can i do to continue this Enhancement ? @mattfarina |
@fudali113 I will target it to 1.19 and we will start bugging you about that soon!! /milestone v1.19 |
ok,i'm ready and i will reopen k/k pr @johnbelamaric |
hi, i'm reopen k/k pr kubernetes/kubernetes#89640 |
Hey there @fudali113, 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19? In order to have this part of the release:
The current release schedule is:
If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍 Thanks! |
Hey @fudali113, I'm following up on my previous update on this Enhancement being part of the Do you happen to have any update on the possiblity of this being included in the release Thanks again for your time and contributions. 🖖 |
Hey @fudali113 / @janetkuo / @soltysh, I'm following up on my previous update on this Enhancement being part of the Do you happen to have any update on the possiblity of this being included in the release Thanks again for your time and contributions. 🖖 |
Hey @fudali113 / @janetkuo / @soltysh, any plans for the Enhancements to be included in Enhancements freeze is on May 19 Note that recently the KEP format has changed. Additionally, #1620 merged recently, adding production readiness review questions to the KEP template. Thanks, |
Hey @fudali113 / @janetkuo / @soltysh, Unfortunately the deadline for the 1.19 Enhancement freeze has passed and the KEP for it is still in flight. For now this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception. |
/milestone clear |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Hi @fudali113 Enhancements Lead here. Any plans for this in 1.20? Thanks! |
/remove-sig scheduling |
Hi @fudali113 Following up: 1.20 Enhancements Freeze is October 6th. Could you let us know if you have plans for 1.20? I don't currently see a KEP attached to this issues. To be included in the milestone: As a note, the format of KEPs has changed. If you could please update and include the missing sections noted above that would be great. See for ref https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template Thanks, |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
This is currently being tracked in #2214 |
@soltysh: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Enhancement Description
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
/sig job
The text was updated successfully, but these errors were encountered: