[MILESTONENOTIFIER] Milestone Issue Needs Approval
@ellenkorbes @juanvallejo @kubernetes/sig-cli-misc
Action required: This issue must have the status/approved-for-milestone
label applied by a SIG maintainer. If the label is not applied within 4 days, the issue will be moved out of the v1.12 milestone.
sig/cli
: Issue will be escalated to these SIGs if needed.priority/important-longterm
: Escalate to the issue owners; move out of the milestone after 1 attempt.kind/cleanup
: Adding tests, refactoring, fixing old bugs.—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
/status approved-for-milestone
[MILESTONENOTIFIER] Milestone Issue: Up-to-date for process
sig/cli
: Issue will be escalated to these SIGs if needed.priority/important-longterm
: Escalate to the issue owners; move out of the milestone after 1 attempt.kind/cleanup
: Adding tests, refactoring, fixing old bugs.—
@soltysh @juanvallejo do we clear this milestone?
@dims yes
/milestone clear
/milestone v1.13
@juanvallejo @ellenkorbes ping, is this on track for 1.13? any related PR?
Yes, this is still open and in-progress, but not something that we will actually finish for 1.13, it'll take us some more time.
thanks!
/milestone v1.14
not there yet,
/milestone clear
@nikopen: The provided milestone is not valid for this repository. Milestones in this repository: [next-candidate
, v1.10
, v1.11
, v1.12
, v1.13
, v1.4
, v1.5
, v1.6
, v1.7
, v1.8
, v1.9
]
Use /milestone clear
to clear the milestone.
In response to this:
thanks!
/milestone v1.14
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.
/milestone v1.14
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecyle rotten
Hello from Bug Triage Shadow . I'd like to remind that code freeze is coming in 3 days (Friday, 8th March). ❄️ 🏔 Is this still planned to be fixed for 1.14?
/remove-lifecycle rotten
/milestone clear
we're in code freeze, doesn't look important. let me know if otherwise.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Closed #64164.
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen
.
Mark the issue as fresh with/remove-lifecycle rotten
.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
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.
—