-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Extend metrics stability #3498
Comments
/sig instrumentation |
/lead-opted-in |
/assign @logicalhan |
/milestone v1.26 |
Hello @logicalhan 👋, 1.26 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
@ruheenaansari34 I've updated the KEP to use the new template. Would you mind reassessing it? I also have a PRR reviewer actively conducting reviews. |
@logicalhan Thanks for updating it. Looks like all the requirements for the Enhancements freeze would be met once the PR is merged. |
Here’s where this enhancement currently stands:
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 |
Hi @logicalhan 👋, Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022. Please ensure the following items are completed:
Let me know if there's any PRs that we should be tracking that aren't mentioned in the issue description. As always, we are here to help should questions come up. Thanks! |
Hello @logicalhan 👋 1.26 Release Docs shadow here! This enhancement is marked as ‘Needs Docs’ for 1.26 release. Thank you! |
This isn't a traditional feature, so it isn't actually guarded by a feature gate but one of the outputs of this work is documentation which I have already merged. |
/remove-label lead-opted-in |
/lead-opted-in |
Hi @logicalhan 👋, 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:
For this enhancement, it looks like there are no code changes. 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 @logicalhan, as @LukeMwila mentioned, please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This placeholder PR must be created by today, March 16, and should be ready for review on Tuesday, March 21. |
/lead-opted-in |
Hello @logicalhan 👋, Enhancements team here. Just checking in as we approach enhancements freeze on Thursday, 16th June 2023.
Here's where this enhancement currently stands:
For this KEP, we would need to update the following:
The status of this enhancement is marked as |
/milestone v1.28 |
Hey @logicalhan The status of this enhancement is marked as |
Hello @logicalhan 👋, 1.28 Docs Shadow here. Does this enhancement work planned for 1.28 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! |
Hey @logicalhan , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023. |
Hey again @logicalhan 👋 Here’s the enhancement’s state for the upcoming code freeze:
For this enhancement, it looks like the following code related PR/s are open and they need to be merged or should be in merge-ready state before the code freeze commences : These are the code related PR/s that I found on this KEP issue
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! |
Hey @logicalhan , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023. |
Hey @logicalhan 👋 Enhancements Lead here, |
|
Hello @logicalhan 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before Tuesday 25th July 2023. Thank you! |
/remove-label lead-opted-in |
/close (as completed) |
@logicalhan: 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
k/enhancements
) update PR(s): KEP-3498: Extend stability classes for Kubernetes metrics framework #3499k/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): add GA requirement for extending metrics stability #4041k/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.
The text was updated successfully, but these errors were encountered: