Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📖 docs: update release notes with jobs #5204

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/book/src/development/releasing.md
Original file line number Diff line number Diff line change
Expand Up @@ -94,3 +94,13 @@ Promote the container images from the staging registry to the production registr
```

1. Update the Title and Description of the Slack channel to point to the new version.

## Post Release Steps

### Create new Prow jobs

If the release is for a new MAJOR.MINOR version (i.e. not a patch release) then you will need to create a new set of prow jobs for the release branch.

This is done by updating the [test-infra](https://github.com/kubernetes/test-infra) repo. For an example of PR see [this](https://github.com/kubernetes/test-infra/pull/33751) for the v2.7 release series.

Consider removing jobs from an old release as well. We should only keep jobs for 4 release branches.