Open pwschuurman opened 2 years ago
You're right I didn't notice that it merged in between :wink:
Hi @pwschuurman, 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.
To opt in, let us know and open a Feature Blog placeholder PR against the website repository by 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.
Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.
hello, @pwschuurman, friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog.
Hey again @pwschuurman 👋, 1.31 Enhancements team here,
Just checking in as we approach code freeze at at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.
Here's where this enhancement currently stands:
approved
and lgtm
labels applied) by the code freeze deadline. This includes tests.For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):
Additionally, please let me know if there are any other PRs in k/k not listed in the description that we should track for this KEP, so that we can maintain accurate status.
If you anticipate missing code freeze, you can file an exception request in advance.
The status of this enhancement is marked as at risk for code freeze
.
Hey again @pwschuurman 👋, 1.31 Enhancements team here,
Just a quick friendly reminder as we approach code freeze in around two weeks time, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.
The current status of this enhancement is marked as at risk for code freeze
. There are a few requirements mentioned in the comment https://github.com/kubernetes/enhancements/issues/3335#issuecomment-2201453017 that still need to be completed.
If you anticipate missing code freeze, you can file an exception request in advance.
Hey again @pwschuurman 👋, 1.31 Enhancements team here,
Just a quick friendly reminder as we approach code freeze next week, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.
The current status of this enhancement is marked as at risk for code freeze
. There are a few requirements mentioned in the comment https://github.com/kubernetes/enhancements/issues/3335#issuecomment-2201453017 that still need to be completed.
If you anticipate missing code freeze, you can file an exception request in advance.
Hey again @pwschuurman 👋, 1.31 Enhancements team here,
Just a quick friendly reminder as we approach code freeze in less than 2 days, at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024.
The current status of this enhancement is marked as at risk for code freeze
. There are a few requirements mentioned in the comment https://github.com/kubernetes/enhancements/issues/3335#issuecomment-2201453017 that still need to be completed.
If you anticipate missing code freeze, you can file an exception request in advance.
Hi @pwschuurman @soltysh, with https://github.com/kubernetes/kubernetes/pull/125374 merged, are we good to mark this KEP as tracked for code freeze?
Hi @sreeram-venkitesh, yes, https://github.com/kubernetes/kubernetes/pull/125374 is the only PR necessary to target 1.31.
Hi @pwschuurman Thanks for confirmation.
Everything seems to be in place for this KEP issue now that the following code implementation PR have been merged.
This enhancement is now marked as tracked for code freeze
for the 1.31 Code Freeze!
@pwschuurman in preparation for the next release, could you kindly update the kep.yaml
file for this KEP to status: implemented
and then close this out?
Hello 👋 1.32 Enhancements Lead here,
I'm closing milestone 1.31 now, If you have more work on this enhancement to complete in v1.32, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.32. Thanks!
/milestone clear
Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.
/remove-label lead-opted-in
Enhancement Description
.spec.ordinals.start
field.k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/3336k/k
) update PR(s): https://github.com/kubernetes/kubernetes/pull/112744k/website
) update PR(s): https://github.com/kubernetes/website/pull/37224k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/3768k/k
) update PR(s): https://github.com/kubernetes/kubernetes/pull/115260k/kube-state-metrics
) update PR(s): https://github.com/kubernetes/kube-state-metrics/pull/1959k/k
) unit PR(s): https://github.com/kubernetes/kubernetes/pull/115536k/k
) integration PR(s): https://github.com/kubernetes/kubernetes/pull/115466k/k
) e2e PR(s): https://github.com/kubernetes/kubernetes/pull/115468k/website
) update(s): https://github.com/kubernetes/website/pull/39823k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/4694k/k
) update PR(s): https://github.com/kubernetes/kubernetes/pull/125374k/kube-state-metrics
) update PR(s): https://github.com/kubernetes/kube-state-metrics/pull/2415k/website
) update(s): https://github.com/kubernetes/website/pull/46719Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.