Open sallyom opened 3 years ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
We definitely can, but we don't need to decide until the start of the 1.31 process. I'll check back in here then
Is it still something we want to consider or have priorities shifted?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
1.32 is coming up soon so please let us know if you want to graduate this to stable.
Having not heard anything in two weeks, I've moved this as not planned for 1.32. Please comment if you disagree
I might have time to graduate this (need to double-check the criterion), but we can add it to the milestone in the meantime.
Moved to proposed so we can discuss who can be revioewer/approver from SIG Node side.
/label lead-opted-in
I might have time to graduate this (need to double-check the criterion), but we can add it to the milestone in the meantime.
@dashpole please ping me on PRs if you plan to move this one forward
Hello @dashpole 👋, Enhancements team here.
Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.
This enhancement is targeting for stage stable
for v1.32 (correct me, if otherwise).
Here's where this enhancement currently stands:
implementable
for latest-milestone: v1.32
.For this KEP, we would just need to update the following:
implementable
for latest-milestone: v1.32
. Risks and Mitigations
, Upgrade/Downgrade Strategy
, and Version Skew Strategy
. Please ensure that all required sections (not marked Optional
in https://github.com/kubernetes/enhancements/blob/master/keps/NNNN-kep-template/README.md`) are present.The status of this enhancement is marked as at risk for enhancement freeze
. Please keep the issue description up-to-date with appropriate stages as well.
If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!
Hello! I'm among the KEP wranglers that sig-node set up to help sig-node KEPs make progress smoothly during the 1.32 timeframe. Hello @dashpole (cc @SergeyKanzhelev ) asking about https://github.com/kubernetes/enhancements/issues/2831#issuecomment-2332565165 do you think you will have capacity to work on this enhancement in the 1.32 cycle? Thanks!
Sorry I forgot previously: PRR freeze on 3rd Oct! If you plan to move forward please post an update for this KEP so you opt in for PRR review! If you plan to move forward please post an update so you opt-in in the PRR review! @sallyom @dashpole
ping @sallyom @dashpole about opting in the PRR review because the deadline is looming
Hello, I'd like to shadow PRR review here, thanks!
Edit: doesn't look like Stable
PRR has been created, will keep an eye here.
/remove-milestone v1.32 /remove-label lead-opted-in
Today's enhancement freeze and I don't see a PR to move this to stable. I am removing this from this release, please let me know if this is a mistake
Hello @dashpole @haircommander 👋, 1.32 Enhancements team here.
Since this enhancement has been rescheduled for a future release, it's now marked as Deferred
for the current v1.32 release cycle. Confirming this based on the comment https://github.com/kubernetes/enhancements/issues/2831#issuecomment-2405227881. Thanks!
/milestone clear
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.