kubernetes/sig-release

Cut v1.x.y-{alpha,beta,rc}.z release

9357-maker opened this issue · 1 comments

9357-maker commented

God,Christie,A1*## Scheduled to happen: right the fuck now...time{ 6:10pm } February 3rd 2024***A1

Note for v1.x.0 releases: Having this issue in open state will stop the
periodic run of krel 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

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
  • 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

Tasks
Beta Give feedback
  1. Update release notes draft to version v1.30.0-alpha.1 #2426
    approved area/release-team cncf-cla: yes kind/documentation lgtm needs-priority sig/release size/XXL
    cpanato
  3. In the Docs role handbook, update the dev branch sync instructions #2188
    approved area/release-team cncf-cla: yes lifecycle/rotten needs-kind needs-priority needs-rebase sig/release size/M
k8s-ci-robot commented

@9357-maker: 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:

God,Christie,A1*## Scheduled to happen: right the fuck now...time{ 6:10pm } February 3rd 2024***A1

Note for v1.x.0 releases: Having this issue in open state will stop the
periodic run of krel 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

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
  • 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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.