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

Manager integration stability and correctness [Part 2] #1939

Open
2 of 12 tasks
rzetelskik opened this issue May 24, 2024 · 5 comments
Open
2 of 12 tasks

Manager integration stability and correctness [Part 2] #1939

rzetelskik opened this issue May 24, 2024 · 5 comments
Assignees
Labels
kind/epic Categorizes issue as an epic. 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.

Comments

@rzetelskik
Copy link
Member

rzetelskik commented May 24, 2024

Part 2 of #1897

Task list

  1. kind/bug priority/important-soon triage/accepted
    rzetelskik
  2. kind/bug priority/important-soon triage/accepted
    rzetelskik
  3. kind/feature priority/important-soon triage/accepted
    rzetelskik
  4. kind/feature priority/important-longterm triage/accepted
    rzetelskik
  5. kind/feature priority/backlog triage/accepted
  6. kind/documentation priority/important-longterm triage/accepted
  7. kind/feature priority/important-longterm triage/accepted
  8. kind/feature priority/backlog triage/accepted
  9. kind/feature priority/backlog triage/accepted
  10. kind/bug priority/important-longterm triage/accepted
    rzetelskik
  11. kind/documentation priority/important-longterm triage/accepted
    rzetelskik

/kind epic
/assign

@scylla-operator-bot scylla-operator-bot bot added kind/epic Categorizes issue as an epic. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels May 24, 2024
@rzetelskik
Copy link
Member Author

rzetelskik commented May 24, 2024

#1827 and #1902 are kind of high priority, but we're waiting for a feature from the manager team. The rest won't make it for 1.13 imo.

@tnozicka tnozicka added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label May 24, 2024
@scylla-operator-bot scylla-operator-bot bot removed the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label May 24, 2024
@rzetelskik
Copy link
Member Author

@tnozicka I also added a couple of issues that I created in the meantime, please verify if all fit here

@tnozicka
Copy link
Member

np, I take it as a rolling one. We'll do the same dance at the end of the next release and make Part 3, if needed.

Copy link
Contributor

The Scylla Operator project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 30d 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out

/lifecycle stale

@scylla-operator-bot scylla-operator-bot bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 11, 2024
@rzetelskik
Copy link
Member Author

/remove-lifecycle stale
/triage accepted

@scylla-operator-bot scylla-operator-bot bot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic Categorizes issue as an epic. 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.
Projects
None yet
Development

No branches or pull requests

2 participants