mirror of
https://github.com/kubernetes-sigs/descheduler.git
synced 2026-01-28 14:41:10 +01:00
Merge pull request #1676 from sanposhiho/email-address-mailing-list
fix: update the mailing list address
This commit is contained in:
@@ -21,7 +21,7 @@ RUN VERSION=${VERSION} make build.$ARCH
|
|||||||
|
|
||||||
FROM scratch
|
FROM scratch
|
||||||
|
|
||||||
MAINTAINER Kubernetes SIG Scheduling <kubernetes-sig-scheduling@googlegroups.com>
|
MAINTAINER Kubernetes SIG Scheduling <sig-scheduling@kubernetes.io>
|
||||||
|
|
||||||
LABEL org.opencontainers.image.source https://github.com/kubernetes-sigs/descheduler
|
LABEL org.opencontainers.image.source https://github.com/kubernetes-sigs/descheduler
|
||||||
|
|
||||||
|
|||||||
@@ -13,7 +13,7 @@
|
|||||||
# limitations under the License.
|
# limitations under the License.
|
||||||
FROM scratch
|
FROM scratch
|
||||||
|
|
||||||
MAINTAINER Kubernetes SIG Scheduling <kubernetes-sig-scheduling@googlegroups.com>
|
MAINTAINER Kubernetes SIG Scheduling <sig-scheduling@kubernetes.io>
|
||||||
|
|
||||||
USER 1000
|
USER 1000
|
||||||
|
|
||||||
|
|||||||
@@ -13,4 +13,4 @@ sources:
|
|||||||
- https://github.com/kubernetes-sigs/descheduler
|
- https://github.com/kubernetes-sigs/descheduler
|
||||||
maintainers:
|
maintainers:
|
||||||
- name: Kubernetes SIG Scheduling
|
- name: Kubernetes SIG Scheduling
|
||||||
email: kubernetes-sig-scheduling@googlegroups.com
|
email: sig-scheduling@kubernetes.io
|
||||||
|
|||||||
@@ -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)
|
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`
|
4. Cut release branch from `master`, eg `release-1.24`
|
||||||
5. Publish release using Github's release process from the git tag you created
|
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**
|
**Patch release**
|
||||||
1. Pick relevant code change commits to the matching release branch, eg `release-1.24`
|
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
|
3. Merge Helm chart version update to release branch
|
||||||
4. Perform the image promotion process for the patch version
|
4. Perform the image promotion process for the patch version
|
||||||
5. Publish release using Github's release process from the git tag you created
|
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
|
### Flowchart
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user