Open dashpole opened 5 years ago
Hello @dashpole π, Enhancements team here.
Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.
This enhancement is targeting for stage beta
for v1.27 (correct me, if otherwise)
Hereβs where this enhancement currently stands:
implementable
for latest-milestone: v1.27
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. π
The status of this enhancement is marked as tracked
. Please keep the issue description up-to-date with appropriate stages as well.
Thank you!
/label tracked/yes
Hi @dashpole, Iβm reaching out from the 1.27 Release Docs team. This enhancement is marked as βNeeds Docsβ for the 1.27 release.
Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.
Please feel free to reach out with any questions. Thanks!
Hi @dashpole π, Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023. Please ensure the following items are completed:
Please let me know what other PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks!
Hi @dashpole the PR in the description looks like an old cancelled Docs PR from 1.26: https://github.com/kubernetes/website/pull/37783. Is there a newer PR for 1.27? Yesterday was the PRs ready for review deadline. If there's not a PR for 1.27, please create and populate one as soon as possible.
Hello again @dashpole, just following up about the Docs PR for this enhancement. I also posted about it in the #sig-instrumentation channel on Slack, but still haven't got a specific response about the PR.
Hello again @dashpole, just following up about the Docs PR for this enhancement. I also posted about it in the #sig-instrumentation channel on Slack, but still haven't got a specific response about the PR.
Hi, @dashpole is on leave, I'll pick up for him in the interim. I've created a docs PR with the changes we deferred from the last release.
Thanks!
/label lead-opted-in
Hello @dashpole π, Enhancements team here.
Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.
This enhancement is targeting for stage stable
for v1.30 (correct me, if otherwise)
Here's where this enhancement currently stands:
implementable
for latest-milestone: 1.30
. For this KEP, we would just need to update the following:
GA
. There is an unanswered question here and the Graduation Requirements for GA are not checkedThe 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. Thank you!
@pnbrown the graduation requirements aren't checked because the GA aspects of the feature are going to be implemented during the 1.30 timeframe. Otherwise, it would already be GA.
PRR review is completed for GA: https://github.com/dashpole/enhancements/blob/47c37e437cecb2d646ae4619485a5a3deac4c056/keps/prod-readiness/sig-instrumentation/647.yaml#L6
I'll update the unanswered question.
That's my mistake
Hello @dashpole π, Enhancements team here.
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze π
Hello @dashpole :wave:, 1.30 Docs Lead here.
Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30
branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 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 @dashpole
π from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!
We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.
To opt in, you need to open a Feature Blog placeholder PR against the website repository. The placeholder PR deadline is 27th February, 2024. Here's the 1.30 Release Calendar
Hey again @dashpole π Enhancements team here,
Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .
Here's where this enhancement currently stands:
approved
and lgtm
labels applied) by the code freeze deadline. This includes tests.Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. As always, we are here to help if any questions come up. Thanks!
@dashpole, Enhancements team here! As this enhancement is targeting stable for this release, may you please update the status field in the kep.yaml file to implemented as the code PRs are merged and the feature gates are removed.
title nit /retitle API Server tracing
Hello @dashpole π, 1.31 Enhancements Lead here.
Since this KEP has graduated to GA in v1.30, please mark the status of the KEP as implemented
here, after which we can close this issue.
/remove-label lead-opted-in
It did not graduate to GA in 1.30
@dashpole Ah my bad, I assumed it was GA after reading https://github.com/kubernetes/enhancements/issues/647#issuecomment-1979075916.
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
Enhancement Description
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement