From 2a27d1be90a4ebae6626fe95e6f3d597041f5db6 Mon Sep 17 00:00:00 2001 From: Kensei Nakada Date: Wed, 30 Apr 2025 11:34:28 +0200 Subject: [PATCH] fix: update the mailing list address --- Dockerfile | 2 +- Dockerfile.dev | 2 +- charts/descheduler/Chart.yaml | 2 +- docs/release-guide.md | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/Dockerfile b/Dockerfile index 3fa6a2b1d..29960abde 100644 --- a/Dockerfile +++ b/Dockerfile @@ -21,7 +21,7 @@ RUN VERSION=${VERSION} make build.$ARCH FROM scratch -MAINTAINER Kubernetes SIG Scheduling +MAINTAINER Kubernetes SIG Scheduling LABEL org.opencontainers.image.source https://github.com/kubernetes-sigs/descheduler diff --git a/Dockerfile.dev b/Dockerfile.dev index c5522f1ca..ddb6225cb 100644 --- a/Dockerfile.dev +++ b/Dockerfile.dev @@ -13,7 +13,7 @@ # limitations under the License. FROM scratch -MAINTAINER Kubernetes SIG Scheduling +MAINTAINER Kubernetes SIG Scheduling USER 1000 diff --git a/charts/descheduler/Chart.yaml b/charts/descheduler/Chart.yaml index 71d9052e7..da02f866b 100644 --- a/charts/descheduler/Chart.yaml +++ b/charts/descheduler/Chart.yaml @@ -13,4 +13,4 @@ sources: - https://github.com/kubernetes-sigs/descheduler maintainers: - name: Kubernetes SIG Scheduling - email: kubernetes-sig-scheduling@googlegroups.com + email: sig-scheduling@kubernetes.io diff --git a/docs/release-guide.md b/docs/release-guide.md index 12d7c9e0d..02ac9c770 100644 --- a/docs/release-guide.md +++ b/docs/release-guide.md @@ -26,7 +26,7 @@ When the above pre-release steps are complete and the release is ready to be cut 3. Perform the [image promotion process](https://github.com/kubernetes/k8s.io/tree/main/k8s.gcr.io#image-promoter). [Example](https://github.com/kubernetes/k8s.io/pull/3344) 4. Cut release branch from `master`, eg `release-1.24` 5. Publish release using Github's release process from the git tag you created -6. Email `kubernetes-sig-scheduling@googlegroups.com` to announce the release +6. Email `sig-scheduling@kubernetes.io` to announce the release **Patch release** 1. Pick relevant code change commits to the matching release branch, eg `release-1.24` @@ -34,7 +34,7 @@ When the above pre-release steps are complete and the release is ready to be cut 3. Merge Helm chart version update to release branch 4. Perform the image promotion process for the patch version 5. Publish release using Github's release process from the git tag you created -6. Email `kubernetes-sig-scheduling@googlegroups.com` to announce the release +6. Email `sig-scheduling@kubernetes.io` to announce the release ### Flowchart