Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Umbrella issue: clarify version, skew, upgrade support #12329

Open
6 of 7 tasks
liggitt opened this issue Jan 22, 2019 · 11 comments
Open
6 of 7 tasks

Umbrella issue: clarify version, skew, upgrade support #12329

liggitt opened this issue Jan 22, 2019 · 11 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. wg/lts Categorizes an issue or PR as relevant to WG LTS.
Projects
WG LTS

Comments

@liggitt
Copy link
Member

liggitt commented Jan 22, 2019 •
edited

This issue tracks follow-up issues from #11060:

#12329 (comment)
This was referenced Jan 22, 2019
Merged
Closed
Closed
Closed
Closed
Closed
Open
Closed
@imkin
Copy link

imkin commented Jan 25, 2019

Some possibly related jira issues.
kubernetes/kubernetes#45506
#12233

@tpepper tpepper added this to In progress in WG LTS Mar 15, 2019
@imkin
Copy link

imkin commented Mar 15, 2019

/wg lts

@k8s-ci-robot k8s-ci-robot added the wg/lts Categorizes an issue or PR as relevant to WG LTS. label Mar 15, 2019
@imkin imkin moved this from In progress to Backlog in WG LTS Mar 15, 2019
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2019
@cblecker cblecker removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 13, 2019
@sftim
Copy link
Contributor

sftim commented Sep 10, 2019

/kind feature
/priority important-longterm
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 10, 2019
@jimangel jimangel mentioned this issue Apr 16, 2020
Merged
@sftim
Copy link
Contributor

sftim commented Oct 8, 2020

/triage accepted

@k8s-ci-robot k8s-ci-robot added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Oct 8, 2020
@nikhita
Copy link
Member

nikhita commented Sep 1, 2022

👋 on a super old issue. Looks like all related PRs are merged. We should be good to close this?

@liggitt
Copy link
Member Author

liggitt commented Sep 1, 2022

👋 looks like three of the closes were because the issues went stale :-/

@sftim
Copy link
Contributor

sftim commented Sep 1, 2022

I'd keep this open until we've got a clear reason to close it.

I agree with maintaining
/lifecycle frozen

@omerbensaadon

This comment was marked as resolved.

Sign in to view
@k8s-triage-robot
Copy link

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

  • Confirm that this issue is still relevant with /triage accepted (org members only)
  • Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. and removed triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jan 19, 2024
@natalisucks
Copy link
Contributor

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on. wg/lts Categorizes an issue or PR as relevant to WG LTS.
Projects
SIG Docs Longterm issues
Status: Triage Accepted
SIG Docs k/website Board
Status: No status
WG LTS
  
Backlog
Milestone
No milestone
Development

No branches or pull requests
10 participants
@liggitt @cblecker @imkin @natalisucks @nikhita @omerbensaadon @k8s-ci-robot @sftim @fejta-bot @k8s-triage-robot