From 36387013e1d261b3c31380bdc71f06d600789832 Mon Sep 17 00:00:00 2001 From: Richard Case Date: Mon, 4 Nov 2024 17:00:32 +0000 Subject: [PATCH] docs: update release notes with jobs Update the release notes to add a reminder that the Prow jobs need to be updated for any new MAJOR.MINOR release. Signed-off-by: Richard Case --- docs/book/src/development/releasing.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/book/src/development/releasing.md b/docs/book/src/development/releasing.md index ae94344ab1..af3756b850 100644 --- a/docs/book/src/development/releasing.md +++ b/docs/book/src/development/releasing.md @@ -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.