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

[2pt] Plan on the dashboard for time to release to prod #2545

Closed
Tracked by #2563
harshad16 opened this issue May 4, 2022 · 5 comments
Closed
Tracked by #2563

[2pt] Plan on the dashboard for time to release to prod #2545

harshad16 opened this issue May 4, 2022 · 5 comments
Assignees
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. sig/observability Categorizes an issue or PR as relevant to SIG Observability triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@harshad16
Copy link
Member

Plan on the dashboard for time to release to prod

@harshad16 harshad16 added the kind/feature Categorizes issue or PR as related to a new feature. label May 4, 2022
@sesheta sesheta added the needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. label May 4, 2022
@harshad16 harshad16 changed the title Plan on the dashboard for time to release to prod [2pt] Plan on the dashboard for time to release to prod May 4, 2022
@harshad16
Copy link
Member Author

/triage accepted
/sig observability

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. sig/observability Categorizes an issue or PR as relevant to SIG Observability and removed needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. labels May 5, 2022
@sesheta
Copy link
Member

sesheta commented Aug 15, 2022

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.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 15, 2022
@sesheta
Copy link
Member

sesheta commented Sep 14, 2022

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.

/lifecycle rotten

@sesheta sesheta 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 Sep 14, 2022
@harshad16
Copy link
Member Author

/remove-lifecycle rotten
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 15, 2022
@harshad16 harshad16 moved this to 🆕 New in Planning Board Oct 7, 2022
@harshad16
Copy link
Member Author

This was part of Q2KR2022, closing the issue
as it was achieved with pipeline releasing application and updating the images.
thank you all for working on this.

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Planning Board Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. sig/observability Categorizes an issue or PR as relevant to SIG Observability triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: Done
Development

No branches or pull requests

5 participants