From 45a721bf10ca4bc282d8dc3d64411e7c346c44f1 Mon Sep 17 00:00:00 2001 From: Carlos Santana Date: Mon, 10 Jan 2022 03:22:01 +0000 Subject: [PATCH] update url for kubernetes-dev mailing list to new location Signed-off-by: Carlos Santana --- .github/ISSUE_TEMPLATE/lead.md | 2 +- .github/ISSUE_TEMPLATE/release-manager.md | 2 +- .github/ISSUE_TEMPLATE/release-team-lead.md | 2 +- leads/onboarding.md | 2 +- release-engineering/role-handbooks/branch-manager.md | 4 ++-- release-engineering/role-handbooks/patch-release-team.md | 4 ++-- release-team/role-handbooks/docs/Release-Timeline.md | 6 +++--- release-team/role-handbooks/enhancements/README.md | 6 +++--- 8 files changed, 14 insertions(+), 14 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/lead.md b/.github/ISSUE_TEMPLATE/lead.md index 1aea1048e5a..eb99922fae6 100644 --- a/.github/ISSUE_TEMPLATE/lead.md +++ b/.github/ISSUE_TEMPLATE/lead.md @@ -24,7 +24,7 @@ hold and only released once approved by a SIG Release (subproject) owner.** - [ ] Has joined the following mailing lists: - [kubernetes-sig-release](https://groups.google.com/forum/#!forum/kubernetes-sig-release) - [kubernetes-release-team](https://groups.google.com/a/kubernetes.io/g/release-team) - - [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) + - [kubernetes-dev](https://groups.google.com/a/kubernetes.io/group/dev) - [kubernetes-announce](https://groups.google.com/forum/#!forum/kubernetes-announce) - [release-managers](https://groups.google.com/a/kubernetes.io/forum/#!forum/release-managers) - [release-managers-private](https://groups.google.com/a/kubernetes.io/forum/#!forum/release-managers-private) diff --git a/.github/ISSUE_TEMPLATE/release-manager.md b/.github/ISSUE_TEMPLATE/release-manager.md index 4eaec9e79a5..8bfeea7c807 100644 --- a/.github/ISSUE_TEMPLATE/release-manager.md +++ b/.github/ISSUE_TEMPLATE/release-manager.md @@ -33,7 +33,7 @@ e.g., permanent, temporary - [ ] Ensure new Release Manager: - [ ] Has joined the following mailing lists: - [kubernetes-sig-release](https://groups.google.com/forum/#!forum/kubernetes-sig-release) - - [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) + - [kubernetes-dev](https://groups.google.com/a/kubernetes.io/group/dev) - [ ] Has joined the following Slack channels: - [#sig-release](https://kubernetes.slack.com/messages/C2C40FMNF) - [#release-management](https://kubernetes.slack.com/messages/CJH2GBF7Y) diff --git a/.github/ISSUE_TEMPLATE/release-team-lead.md b/.github/ISSUE_TEMPLATE/release-team-lead.md index fcdd07a150f..1e125c1ece3 100644 --- a/.github/ISSUE_TEMPLATE/release-team-lead.md +++ b/.github/ISSUE_TEMPLATE/release-team-lead.md @@ -26,7 +26,7 @@ e.g., Kubernetes 1.18 - [ ] Ensure new Release Team Lead: - [ ] Has joined the following mailing lists: - [kubernetes-sig-release](https://groups.google.com/forum/#!forum/kubernetes-sig-release) - - [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) + - [kubernetes-dev](https://groups.google.com/a/kubernetes.io/group/dev) - [ ] Has joined the following Slack channels: - [#sig-release](https://kubernetes.slack.com/messages/C2C40FMNF) - [#release-management](https://kubernetes.slack.com/messages/CJH2GBF7Y) diff --git a/leads/onboarding.md b/leads/onboarding.md index 6a5672519a4..248039d3067 100644 --- a/leads/onboarding.md +++ b/leads/onboarding.md @@ -15,7 +15,7 @@ To ensure quality communication SIG Release Chairs and Technical Leads should: - kubernetes-release-team: https://groups.google.com/a/kubernetes.io/g/release-team - kubernetes-dev: - https://groups.google.com/forum/#!forum/kubernetes-dev + https://groups.google.com/a/kubernetes.io/group/dev - kubernetes-announce: https://groups.google.com/forum/#!forum/kubernetes-announce - release-managers: diff --git a/release-engineering/role-handbooks/branch-manager.md b/release-engineering/role-handbooks/branch-manager.md index a9b75560093..b54865c8f10 100644 --- a/release-engineering/role-handbooks/branch-manager.md +++ b/release-engineering/role-handbooks/branch-manager.md @@ -185,7 +185,7 @@ krel announce send --tag vX.Y.0-{alpha,beta,rc}.Z --name "" --name Note: To view this document, you will need to join the [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) Google group. +> Note: To view this document, you will need to join the [kubernetes-dev](https://groups.google.com/a/kubernetes.io/group/dev) Google group. [image-promotion]: https://sigs.k8s.io/promo-tools/docs/promotion-pull-requests.md [kubernetes-release-team]: https://groups.google.com/a/kubernetes.io/g/release-team diff --git a/release-engineering/role-handbooks/patch-release-team.md b/release-engineering/role-handbooks/patch-release-team.md index 1f138b9d72e..28908b4051e 100644 --- a/release-engineering/role-handbooks/patch-release-team.md +++ b/release-engineering/role-handbooks/patch-release-team.md @@ -464,7 +464,7 @@ whenever possible to give updates on activity in your release branch When you have a plan for the next patch release, send an announcement ([example](https://groups.google.com/forum/#!topic/kubernetes-dev-announce/HGYsjOFtcdU)): -* TO: [kubernetes-dev@googlegroups.com](https://groups.google.com/forum/#!forum/kubernetes-dev) +* TO: [kubernetes-dev@googlegroups.com](https://groups.google.com/a/kubernetes.io/group/dev) * *BCC*: [kubernetes-dev-announce@googlegroups.com](https://groups.google.com/forum/#!forum/kubernetes-dev-announce) several working days in advance, including a release notes preview. Also @@ -595,7 +595,7 @@ corresponding command line help (`-h`) outputs. | Package creation (needs its own improved workflow; work starting on that) | Ping [Build Admins](https://git.k8s.io/sig-release/release-managers.md#build-admins) by name on Slack for package building | | Package testing (needs improvement) | Visually validate [yum repo](https://packages.cloud.google.com/yum/repos/kubernetes-el7-x86_64/repodata/primary.xml) and [apt repo](https://packages.cloud.google.com/apt/dists/kubernetes-xenial/main/binary-amd64/Packages) have entries for "1.13.3" in package NVRs (Name-Version-Release) | | Official email notify | ```krel announce send --tag v1.13.3 --nomock``` | -| Check mail arrives | manual/visual check that [k-announce](https://groups.google.com/forum/#!forum/kubernetes-announce) and [k-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) got mail OK | +| Check mail arrives | manual/visual check that [k-announce](https://groups.google.com/forum/#!forum/kubernetes-announce) and [k-dev](https://groups.google.com/a/kubernetes.io/group/dev) got mail OK | | Completion | n/a | [release-managers]: /release-managers.md#release-managers diff --git a/release-team/role-handbooks/docs/Release-Timeline.md b/release-team/role-handbooks/docs/Release-Timeline.md index e10747dca20..f3b4ca193c2 100644 --- a/release-team/role-handbooks/docs/Release-Timeline.md +++ b/release-team/role-handbooks/docs/Release-Timeline.md @@ -80,7 +80,7 @@ These steps take approximately one hour to complete, and should be completed imm - ⚠️ Join these Google groups: - [kubernetes-sig-release](https://groups.google.com/forum/#!forum/kubernetes-sig-release) - [kubernetes-sig-docs](https://groups.google.com/forum/#!forum/kubernetes-sig-docs) - - [kubernetes-dev](https://groups.google.com/forum/#!forum/kubernetes-dev) + - [kubernetes-dev](https://groups.google.com/a/kubernetes.io/group/dev) - [kubernetes-release-team](https://groups.google.com/a/kubernetes.io/g/release-team) - ⚠️ List of members for this group is managed in git. Please create a PR against `kuberenetes/sig-release` repo to include your email under `release-team` group in [`sig-release/group.yaml`](https://github.com/kubernetes/k8s.io/blob/main/groups/sig-release/groups.yaml) - [kubernetes-release-team-shadows](https://groups.google.com/a/kubernetes.io/g/release-team-shadows) @@ -155,7 +155,7 @@ Send a Slack message to those that you select, e.g: You'll then want to join these mailing lists if you haven't already: >- https://groups.google.com/forum/#!forum/kubernetes-sig-release >- https://groups.google.com/forum/#!forum/kubernetes-sig-docs ->- https://groups.google.com/forum/#!forum/kubernetes-dev +>- https://groups.google.com/a/kubernetes.io/group/dev > >Access to Google docs and calendar invites are often based on these mailing lists, so it's a good idea to subscribe. > @@ -282,7 +282,7 @@ This is very helpful for weekly reports and managing deadlines ### Communicate major deadlines -The Release Lead and Enhancements Lead will send announcements to the [Kubernetes Dev Group](https://groups.google.com/forum/#!forum/kubernetes-dev) periodically during the release cycle. +The Release Lead and Enhancements Lead will send announcements to the [Kubernetes Dev Group](https://groups.google.com/a/kubernetes.io/group/dev) periodically during the release cycle. Communicate with the Release Lead and Enhancements Lead to include the Doc Placeholder PR, Doc PR Ready-for-Review, and Docs Complete deadlines in their announccements. COMMUNICATE ALL 3 MAJOR DATES AT LEAST A WEEK PRIOR, INCLUDING THE RELEASE DATE REPO FREEZE, FOLLOWING THE BELOW METHODS: diff --git a/release-team/role-handbooks/enhancements/README.md b/release-team/role-handbooks/enhancements/README.md index cede3bde873..7a360ef1a5e 100644 --- a/release-team/role-handbooks/enhancements/README.md +++ b/release-team/role-handbooks/enhancements/README.md @@ -118,7 +118,7 @@ It is important that this process be followed and documentation remain up-to-dat #### Pre-Enhancements Freeze (Week 1) -- Send an email to the [Kubernetes-Dev](https://groups.google.com/forum/#!forum/kubernetes-dev) mailing list and a message to #chairs-and-techleads slack channel with a call for enhancements and how to opt-in to the release. +- Send an email to the [Kubernetes-Dev](https://groups.google.com/a/kubernetes.io/group/dev) mailing list and a message to #chairs-and-techleads slack channel with a call for enhancements and how to opt-in to the release. - Verify issues have k/k PRs associated so they can be referenced and easily tracked. This is going to be critical come Enhancement Freeze and Code Freeze to see the status of the code. - Work with the Release Lead to introduce yourself, talk about release information, and relay information about opting into the release with SIG Leads. - Weekly Release meetings require updates of current status. Use the `Feature stats` tab to update the release team on counts of enhancements in good and bad progress. @@ -135,11 +135,11 @@ It is important that this process be followed and documentation remain up-to-dat - Stay on top of comments in issues when owners respond and update their status in the sheet if necessary. - Mark features as `At Risk` if there is no communication, active PRs on the issues, or it is missing other requirements coming into Enhancement Freeze. - Start syncing with Communications Team on giving an induction what's coming up for the release. -- Send an email to [Kubernetes-Dev](https://groups.google.com/forum/#!forum/kubernetes-dev) that Enhancement freeze is coming and share current Enhancements status. Examples [1](https://groups.google.com/g/kubernetes-dev/c/-nTNtBBHL2Y/m/WfNzb_E1EAAJ). +- Send an email to [Kubernetes-Dev](https://groups.google.com/a/kubernetes.io/group/dev) that Enhancement freeze is coming and share current Enhancements status. Examples [1](https://groups.google.com/g/kubernetes-dev/c/-nTNtBBHL2Y/m/WfNzb_E1EAAJ). #### Enhancements Freeze (Week 3) -- On Freeze day, send an email to [Kubernetes-Dev](https://groups.google.com/forum/#!forum/kubernetes-dev) that freeze has happened and upcoming key dates. Examples [1](https://groups.google.com/g/kubernetes-dev/c/JDM7bNKvhqQ/m/8S7BXtXPBQAJ). +- On Freeze day, send an email to [Kubernetes-Dev](https://groups.google.com/a/kubernetes.io/group/dev) that freeze has happened and upcoming key dates. Examples [1](https://groups.google.com/g/kubernetes-dev/c/JDM7bNKvhqQ/m/8S7BXtXPBQAJ). - Remove [SIG Leads Google Group][sig-leads-group]'s access to the `KEP Collection` sheets on the enhancement collection sheet. - Remove any enhancements that failed to meet the criteria by the Enhancement freeze deadline. - Set their status in the sheet to `Removed from Milestone` and use the `Enhancements` -> `Remove Enhancements from Milestone` menu option to move them over to the `Removed from milestone` tab.