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

Ensure groups.google.com/g/kubernetes-release-team is properly archived #1811

Closed
jeremyrickard opened this issue Jan 12, 2022 · 10 comments
Closed

Ensure groups.google.com/g/kubernetes-release-team is properly archived #1811

jeremyrickard opened this issue Jan 12, 2022 · 10 comments
Assignees
@justaugustus @jeremyrickard
Labels
kind/documentation Categorizes issue or PR as related to documentation. 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
Release Team SIG Release

Comments

@jeremyrickard
Copy link
Contributor

With the introduction of the release-team@ google group, the old list should be in archived/no sending mode.

Ref: https://kubernetes.slack.com/archives/C2C40FMNF/p1642001447091100

We should:

[ ] Review all handbooks to ensure it's not referenced anywhere
[ ] Update lead handbook to reference it being deprecated and that it shouldn't be added to any document sharing
[ ] Ensure that the list is properly put into archived mode.

/sig release
/priority important-soon
/kind documentation
@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. labels Jan 12, 2022
@jeremyrickard
Copy link
Contributor Author

@justaugustus I'll take a look through the handbooks if you can handle the mailing list management.

@jeremyrickard jeremyrickard added this to Backlog (high-priority at top) in Release Team via automation Jan 12, 2022
@justaugustus justaugustus added this to To do in SIG Release Jan 25, 2022
@k8s-triage-robot
Copy link

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 Apr 12, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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 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 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 12, 2022
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active 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:

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

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

/close

@k8s-ci-robot
Copy link
Contributor

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active 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:

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

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

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

Release Team automation moved this from Backlog (high-priority at top) to Done (1.22) Jun 11, 2022
SIG Release automation moved this from To do to Done/Closed Jun 11, 2022
@palnabarun
Copy link
Member

/reopen
/remove-lifecycle rotten

@k8s-ci-robot
Copy link
Contributor

@palnabarun: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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.

@k8s-ci-robot k8s-ci-robot reopened this Jun 11, 2022
SIG Release automation moved this from Done/Closed to In progress Jun 11, 2022
Release Team automation moved this from Done (1.22) to In progress Jun 11, 2022
@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 Jun 11, 2022
@palnabarun
Copy link
Member

(until this is verified to be done)

@palnabarun palnabarun moved this from In progress to Backlog (high-priority at top) in Release Team Jun 11, 2022
@jeremyrickard
Copy link
Contributor Author

Verified that both the web posting and email posting are disabled.

/close

@k8s-ci-robot
Copy link
Contributor

@jeremyrickard: Closing this issue.

In response to this:

Verified that both the web posting and email posting are disabled.

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

Release Team automation moved this from Backlog (high-priority at top) to Done (1.22) Sep 6, 2022
SIG Release automation moved this from In progress to Done/Closed Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justaugustus justaugustus

@jeremyrickard jeremyrickard

Labels
kind/documentation Categorizes issue or PR as related to documentation. 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
Release Team
  
Done (1.22)
SIG Release
  
Done/Closed
Milestone
No milestone
Development

No branches or pull requests
5 participants
@justaugustus @palnabarun @k8s-ci-robot @jeremyrickard @k8s-triage-robot