Cut v1.28.11 release
Verolop opened this issue · 3 comments
Scheduled to happen: Tue, 2024-06-10
Release Blocking Issues
Release Steps
- Create a thread on #release-management: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1718095517960599
- Screenshot unhealthy release branch testgrid boards
- Check the health of the publishing-bot
- Mock Run
- Stage
- Release
- NoMock Run
- Stage
- Image Promotion: kubernetes/k8s.io#6883
- Release
- Notify #release-management: Link to Slack
- Send notification: https://groups.google.com/a/kubernetes.io/g/dev/c/F0UqwIlQOuQ/m/ZdeKfRnVAAAJ
- Update
schedule.yaml
file with the latest release usingschedule-builder
- 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 --type alpha --branch release-1.28 |
https://console.cloud.google.com/cloud-build/builds/fb5b1319-ed16-4a86-92b3-14b5edd61522?project=648026197307 | 2024-06-11 | 01:12:14 | Yes, but at the moment, Go security updates are not done. We still have cherry-picks that are not merged. |
Mock stage | krel stage --type alpha --branch release-1.28 |
https://console.cloud.google.com/cloud-build/builds/fba499a1-9acd-48db-8d62-d4665ba6e1fb?project=648026197307 | 01:12:30 | YES | |
Mock release | krel release --type official --branch release-1.28 --build-version v1.28.10-28+3f88893345ef4a |
https://console.cloud.google.com/cloud-build/builds/f9161ba1-e8a2-4e5b-b643-9eec253be6be?project=648026197307 | 00:16:09 | YES | |
Stage | krel stage --type official --branch release-1.28 --build-version v1.28.10-28+3f88893345ef4a --nomock |
https://console.cloud.google.com/cloud-build/builds/966ba9ec-03a9-4855-b159-042630616d8c?project=648026197307 | 01:29:10 | YES | |
Release | krel release --nomock --type official --branch release-1.28 --build-version v1.28.10-28+3f88893345ef4a |
https://console.cloud.google.com/cloud-build/builds/8516bc10-a9f3-42b3-86af-11aa1f5940b9?project=648026197307 | 00:15:56 | YES |
Action Items
Open Questions
/milestone
/assign
/cc @kubernetes/release-managers
/priority important-soon
/kind documentation
@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:
Scheduled to happen: Tue, 2024-06-10
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 with the latest release usingschedule-builder
- Collect metrics and add them to the
Release steps
table belowRelease 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
The release is done, so closing this issue.
I have updated the issue description.
/close
@mehabhalodiya: Closing this issue.
In response to this:
The release is done, so closing this issue.
/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-sigs/prow repository.