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

Charter clarifications #378

Closed
spiffxp opened this issue Nov 20, 2018 · 7 comments · Fixed by kubernetes/community#5409
Closed

Charter clarifications #378

spiffxp opened this issue Nov 20, 2018 · 7 comments · Fixed by kubernetes/community#5409
Assignees
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@spiffxp
Copy link
Member

spiffxp commented Nov 20, 2018

I requested a number of non-blocking changes to the charter kubernetes/community#2919

Discussed during SIG Release meeting and it was suggested I assign a follow up issue to ensure we don't lose track

/assign @tpepper @justaugustus @calebamiles
as SIG chairs

@spiffxp
Copy link
Member Author

spiffxp commented Jan 4, 2019

/sig release

@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jan 4, 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 Apr 4, 2019
@justaugustus
Copy link
Member

/lifecycle frozen
/remove-lifecycle stale
/milestone v1.15

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 22, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.15 milestone Apr 22, 2019
@justaugustus
Copy link
Member

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label May 1, 2019
@spiffxp
Copy link
Member Author

spiffxp commented Jul 23, 2019

Ping, I feel like recent work on release-engineering is falling into some of these gaps, WDYT about updating the charter to reflect this?

@idealhack idealhack modified the milestones: v1.15, v1.16 Jul 29, 2019
@justaugustus
Copy link
Member

/milestone v1.17
/kind documentation cleanup

@k8s-ci-robot k8s-ci-robot added the kind/documentation Categorizes issue or PR as related to documentation. label Sep 23, 2019
@k8s-ci-robot k8s-ci-robot modified the milestones: v1.16, v1.17 Sep 23, 2019
@k8s-ci-robot k8s-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Sep 23, 2019
@justaugustus justaugustus modified the milestones: v1.17, v1.18 Dec 4, 2019
@justaugustus
Copy link
Member

/assign @saschagrunert
/unassign @tpepper @calebamiles
/milestone v1.21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants