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.

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

Move mount library to staging #2261

Closed
4 tasks
msau42 opened this issue Jan 13, 2021 · 11 comments
Closed
4 tasks

Move mount library to staging #2261

msau42 opened this issue Jan 13, 2021 · 11 comments
Assignees
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/storage Categorizes an issue or PR as relevant to SIG Storage.

Comments

@msau42
Copy link
Member

msau42 commented Jan 13, 2021

Enhancement Description

  • One-line enhancement description (can be used as a release note): Move mount library from k8s.io/utils to k/k/staging
  • Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/2261-staging-mount-library
  • Discussion Link:
  • Primary contact (assignee): brahmaroutu
  • Responsible SIGs: storage
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y): n/a
    • Beta release target (x.y): n/a
    • Stable release target (x.y): 1.20
  • Stable
    • KEP (k/enhancements) update PR(s):
    • Code (k/k) update PR(s):
    • Docs (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.

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 13, 2021
@msau42
Copy link
Member Author

msau42 commented Jan 13, 2021

/sig storage

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 13, 2021
@msau42
Copy link
Member Author

msau42 commented Jan 13, 2021

/assign @brahmaroutu

@xing-yang
Copy link
Contributor

xing-yang commented Jan 14, 2021

@xing-yang
Copy link
Contributor

xing-yang commented Jan 14, 2021

Should this issue be closed if it is already stable in 1.20?

@msau42
Copy link
Member Author

msau42 commented Jan 14, 2021

I believe @brahmaroutu still has a few remaining PRs to wrap up the work

@fejta-bot
Copy link

fejta-bot commented Apr 14, 2021

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-contributor-experience at kubernetes/community.
/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 Apr 14, 2021
@fejta-bot
Copy link

fejta-bot commented May 14, 2021

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-contributor-experience at kubernetes/community.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 14, 2021
@msau42
Copy link
Member Author

msau42 commented May 14, 2021

/remove-lifecycle rotten

Remaining cleanup prs:
kubernetes/utils#191
kubernetes/kubernetes#96130

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label May 14, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 12, 2021

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/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 Aug 12, 2021
@msau42
Copy link
Member Author

msau42 commented Aug 12, 2021

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Aug 12, 2021

@msau42: Closing this issue.

In response to this:

/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Development

No branches or pull requests

6 participants