kubernetes / sig-release

Repo for SIG release
Apache License 2.0
536 stars 385 forks source link

Cut 1.27.12 release #2455

Open Verolop opened 6 months ago

Verolop commented 6 months ago

Scheduled to happen: Wed, 2024-03-13

Release Blocking Issues

Release Steps

Release Tools Version

GitVersion:    vM.m.p
GitCommit:     191ddd0b0b49af1adb04a98e45cebdd36cae9307
GitTreeState:  clean
BuildDate:     YYYY-MM-DDTHH:mm:ssZ
GoVersion:     go1.16.3
Compiler:      gc
Platform:      linux/amd64

Release Jobs History

Step Command Link Start Duration Succeeded?
Mock stage krel stage [arguments]
Mock release krel release [arguments]
Stage krel stage [arguments]
Release krel release [arguments]

Action Items

Open Questions

/milestone /assign /cc @kubernetes/release-managers /priority important-soon /kind documentation

k8s-ci-robot commented 6 months ago

@Verolop: The provided milestone is not valid for this repository. Milestones in this repository: [next, v.1.25, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28, v1.29, v1.30, v1.31, v1.32]

Use /milestone clear to clear the milestone.

In response to [this](https://github.com/kubernetes/sig-release/issues/2455): >## Scheduled to happen: Wed, 2024-03-13 > > >## Release Blocking Issues > > > > >## Release Steps > >- [ ] Create a thread on #release-management: >- [ ] Screenshot unhealthy release branch testgrid boards >- [ ] Check the health of the publishing-bot >- Mock Run > - [ ] Stage > - [ ] Release >- NoMock Run > - [ ] Stage > - [ ] Image Promotion: > - [ ] Release >- [ ] Notify #release-management: >- [ ] Send notification: >- [ ] Update [`schedule.yaml` file](https://github.com/kubernetes/website/blob/main/data/releases/schedule.yaml) with the latest release >- [ ] Collect metrics and add them to the `Release steps` table below > > >## Release Tools Version > > >``` >GitVersion: vM.m.p >GitCommit: 191ddd0b0b49af1adb04a98e45cebdd36cae9307 >GitTreeState: clean >BuildDate: YYYY-MM-DDTHH:mm:ssZ >GoVersion: go1.16.3 >Compiler: gc >Platform: linux/amd64 >``` > >## Release Jobs History > > >| Step | Command | Link | Start | Duration | Succeeded? | >| --- | --- | --- | --- | --- | --- | >| Mock stage | `krel stage [arguments]` | | | | | >| Mock release | `krel release [arguments]` | | | | | >| Stage | `krel stage [arguments]` | | | | | >| Release | `krel release [arguments]` | | | | | > >## Action Items > > > >## Open Questions > > > >/milestone >/assign >/cc @kubernetes/release-managers >/priority important-soon >/kind documentation > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
k8s-ci-robot commented 6 months ago

@Verolop: The provided milestone is not valid for this repository. Milestones in this repository: [next, v.1.25, v1.16, v1.17, v1.18, v1.19, v1.20, v1.21, v1.22, v1.23, v1.24, v1.25, v1.26, v1.27, v1.28, v1.29, v1.30, v1.31, v1.32]

Use /milestone clear to clear the milestone.

In response to [this](https://github.com/kubernetes/sig-release/issues/2455#issuecomment-1994246013): >/milestone 1.27 Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
Verolop commented 6 months ago

/milestone v1.27

Verolop commented 6 months ago

Testgrid dashboards for 1.27

Boards checked for FAILING:

No FAILING Jobs

comment generated by krel

saschagrunert commented 5 months ago

@Verolop do you mind updating the docs in the first comment and then close this one?

k8s-triage-robot commented 2 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 month ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle rotten