Open jsturtevant opened 1 month ago
/sig windows /sig node
Hello @jsturtevant 👋, v1.32 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 alpha
for v1.32 (correct me, if otherwise)
/stage alpha
Here's where this enhancement currently stands:
implementable
for latest-milestone: v1.32
.For this KEP, we would need to update the following:
It looks like https://github.com/kubernetes/enhancements/pull/4888 will address most of these issues.
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!
/cc
/milestone v1.32
Hi @jsturtevant 👋, v1.32 Enhancements team here.
Just a quick friendly reminder as we approach the enhancements freeze later this week, at 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.
The current status of this enhancement is marked as at risk for enhancement freeze
. There are a few requirements mentioned in the comment https://github.com/kubernetes/enhancements/issues/4885#issuecomment-2384510129 that still need to be completed.
If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!
Hello @jsturtevant 👋, v1.32 Enhancements team here,
Now that PR https://github.com/kubernetes/enhancements/pull/4888 has been merged, all the KEP requirements are in place and merged into k/enhancements.
During the release cycle, it would be appreciated if following nits could be addressed:
Update issue description to add direct link to KEP README.md.
Ensure this issue has an assignee.
Aside from the minor nits mentioned above, this enhancement is all good for the upcoming enhancements freeze. 🚀
The status of this enhancement is now marked as tracked for enhancement freeze
. Please keep the issue description up-to-date with appropriate stages as well. Thank you!
/assign @jsturtevant
Hi @jsturtevant 👋, 1.32 Release Docs Lead here.
Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
Hi @jsturtevant 👋, 1.32 Release Docs Lead here.
Does this enhancement work planned for 1.32 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.
Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!
Hi @jsturtevant 👋,
Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here). The deadline for this is a week away at Thursday October 24, 2024 18:00 PDT.
Thanks,
Daniel
Hey again @jsturtevant 👋 v1.32 Enhancements team here,
Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 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 or not linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status.
The status of this enhancement is marked as at risk for code freeze
.
If you anticipate missing code freeze, you can file an exception request in advance. Thank you!
👋 Hi there, William here from v1.32 Comms We'd love for you to consider writing 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 30th Oct 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.
Hey again @jsturtevant 👋, v1.32 Enhancements team here,
Just a quick friendly reminder as we approach code freeze in few days, at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 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/4885#issuecomment-2425347384 that still need to be completed.
If you anticipate missing code freeze, you can file an exception request in advance.
Hello @jsturtevant 👋, v1.32 Enhancements team here
With all the implementation(code related) PRs merged in k/k as per the issue description:
(Its being noted that one PR mentioned in the description that is outside of kubernetes org https://github.com/opencontainers/runtime-spec/pull/1258/ )
This enhancement is now marked as tracked for code freeze
for the v1.32 Code Freeze!
Enhancement Description
k/enhancements
) update PR(s): https://github.com/kubernetes/enhancements/pull/4888k/k
) update PR(s):k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.