k8s-ci-robot
commented
4 months ago @mehabhalodiya: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.
In response to [this](https://github.com/kubernetes/sig-release/issues/2517):
>## Scheduled to happen: Tuesday, 2024-05-04
>
>_Note for v1.x.0 releases: Having this issue in open state will stop the
>periodic run of [`krel fast-forward`](https://testgrid.k8s.io/sig-release-releng-blocking#git-repo-kubernetes-fast-forward)
>to avoid conflicts with releases running in parallel. The fast-forward will
>automatically stop once the v1.x.0 tag is available._
>
>## Release Blocking Issues
>
>Refer to the slack thread: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1717404704745279
>
>
>## 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 using [`schedule-builder`](https://github.com/kubernetes/release/tree/master/cmd/schedule-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 [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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
mehabhalodiya
puerco
Scheduled to happen: Tuesday, 2024-06-04
Note for v1.x.0 releases: Having this issue in open state will stop the periodic run of
krel fast-forwardto avoid conflicts with releases running in parallel. The fast-forward will automatically stop once the v1.x.0 tag is available.Release Blocking Issues
Refer to the slack thread: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1717404704745279
New Release Date: 12th June, 2024 (as per this comment: https://kubernetes.slack.com/archives/CJH2GBF7Y/p1718016847874549?thread_ts=1717404704.745279&cid=CJH2GBF7Y)
Release Steps
schedule.yamlfile with the latest release usingschedule-builderRelease stepstable belowRelease Tools Version
Release Jobs History
mock stagekrel stage --type alpha --branch master --build-version v1.31.0-alpha.0.1211+0aab2a3534927cmock releasekrel release --type alpha --branch master --build-version v1.31.0-alpha.0.1211+0aab2a3534927cstagekrel stage --type alpha --branch master --build-version v1.31.0-alpha.0.1217+a06568062c41b4 --nomockreleasekrel release --type alpha --branch master --build-version v1.31.0-alpha.0.1217+a06568062c41b4 --nomockreleasekrel release --type alpha --branch master --build-version v1.31.0-alpha.0.1217+a06568062c41b4 --nomockAction Items
Open Questions
/milestone v1.31 /assign @mehabhalodiya /cc @kubernetes/release-managers /priority important-soon /kind documentation