@@ -12,38 +12,39 @@ This document details the responsibilities and tasks for each role in the releas
12
12
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
13
13
** Table of Contents**
14
14
15
- - [ Release Lead] ( #release-lead )
16
- - [ Responsibilities] ( #responsibilities )
17
- - [ Tasks] ( #tasks )
18
- - [ Set a tentative release date for the minor release] ( #set-a-tentative-release-date-for-the-minor-release )
19
- - [ Assemble release team] ( #assemble-release-team )
20
- - [ Finalize release schedule and team] ( #finalize-release-schedule-and-team )
21
- - [ Prepare main branch for development of the new release] ( #prepare-main-branch-for-development-of-the-new-release )
22
- - [ Create a new GitHub milestone for the next release] ( #create-a-new-github-milestone-for-the-next-release )
23
- - [[ Track] Remove previously deprecated code] ( #track-remove-previously-deprecated-code )
24
- - [[ Track] Bump dependencies] ( #track-bump-dependencies )
25
- - [ Create a release branch] ( #create-a-release-branch )
26
- - [[ Continuously] Maintain the GitHub release milestone] ( #continuously-maintain-the-github-release-milestone )
27
- - [[ Repeatedly] Cut a release] ( #repeatedly-cut-a-release )
28
- - [[ Optional] [ Track] Bump the Cluster API apiVersion] ( #optional-track-bump-the-cluster-api-apiversion )
29
- - [[ Optional] [ Track] Bump the Kubernetes version] ( #optional-track-bump-the-kubernetes-version )
30
- - [ Communications/Docs/Release Notes Manager] ( #communicationsdocsrelease-notes-manager )
31
- - [ Responsibilities] ( #responsibilities-1 )
32
- - [ Tasks] ( #tasks-1 )
33
- - [ Add docs to collect release notes for users and migration notes for provider implementers] ( #add-docs-to-collect-release-notes-for-users-and-migration-notes-for-provider-implementers )
34
- - [ Update supported versions] ( #update-supported-versions )
35
- - [ Ensure the book for the new release is available] ( #ensure-the-book-for-the-new-release-is-available )
36
- - [ Polish release notes] ( #polish-release-notes )
37
- - [ Change production branch in Netlify to the new release branch] ( #change-production-branch-in-netlify-to-the-new-release-branch )
38
- - [ Update clusterctl links in the quickstart] ( #update-clusterctl-links-in-the-quickstart )
39
- - [ Continuously: Communicate key dates to the community] ( #continuously-communicate-key-dates-to-the-community )
40
- - [ CI Signal/Bug Triage/Automation Manager] ( #ci-signalbug-triageautomation-manager )
41
- - [ Responsibilities] ( #responsibilities-2 )
42
- - [ Tasks] ( #tasks-2 )
43
- - [ Setup jobs and dashboards for a new release branch] ( #setup-jobs-and-dashboards-for-a-new-release-branch )
44
- - [[ Continuously] Monitor CI signal] ( #continuously-monitor-ci-signal )
45
- - [[ Continuously] Reduce the amount of flaky tests] ( #continuously-reduce-the-amount-of-flaky-tests )
46
- - [[ Continuously] Bug triage] ( #continuously-bug-triage )
15
+ - [ Release Tasks] ( #release-tasks )
16
+ - [ Release Lead] ( #release-lead )
17
+ - [ Responsibilities] ( #responsibilities )
18
+ - [ Tasks] ( #tasks )
19
+ - [ Set a tentative release date for the minor release] ( #set-a-tentative-release-date-for-the-minor-release )
20
+ - [ Assemble release team] ( #assemble-release-team )
21
+ - [ Finalize release schedule and team] ( #finalize-release-schedule-and-team )
22
+ - [ Prepare main branch for development of the new release] ( #prepare-main-branch-for-development-of-the-new-release )
23
+ - [ Create a new GitHub milestone for the next release] ( #create-a-new-github-milestone-for-the-next-release )
24
+ - [ \[ Track\] Remove previously deprecated code] ( #track-remove-previously-deprecated-code )
25
+ - [ \[ Track\] Bump dependencies] ( #track-bump-dependencies )
26
+ - [ Create a release branch] ( #create-a-release-branch )
27
+ - [ \[ Continuously\] Maintain the GitHub release milestone] ( #continuously-maintain-the-github-release-milestone )
28
+ - [ \[ Repeatedly\] Cut a release] ( #repeatedly-cut-a-release )
29
+ - [ \[ Optional\] \[ Track\] Bump the Cluster API apiVersion] ( #optional-track-bump-the-cluster-api-apiversion )
30
+ - [ \[ Optional\] \[ Track\] Bump the Kubernetes version] ( #optional-track-bump-the-kubernetes-version )
31
+ - [ Communications/Docs/Release Notes Manager] ( #communicationsdocsrelease-notes-manager )
32
+ - [ Responsibilities] ( #responsibilities-1 )
33
+ - [ Tasks] ( #tasks-1 )
34
+ - [ Add docs to collect release notes for users and migration notes for provider implementers] ( #add-docs-to-collect-release-notes-for-users-and-migration-notes-for-provider-implementers )
35
+ - [ Update supported versions] ( #update-supported-versions )
36
+ - [ Ensure the book for the new release is available] ( #ensure-the-book-for-the-new-release-is-available )
37
+ - [ Polish release notes] ( #polish-release-notes )
38
+ - [ Change production branch in Netlify to the new release branch] ( #change-production-branch-in-netlify-to-the-new-release-branch )
39
+ - [ Update clusterctl links in the quickstart] ( #update-clusterctl-links-in-the-quickstart )
40
+ - [ Continuously: Communicate key dates to the community] ( #continuously-communicate-key-dates-to-the-community )
41
+ - [ CI Signal/Bug Triage/Automation Manager] ( #ci-signalbug-triageautomation-manager )
42
+ - [ Responsibilities] ( #responsibilities-2 )
43
+ - [ Tasks] ( #tasks-2 )
44
+ - [ Setup jobs and dashboards for a new release branch] ( #setup-jobs-and-dashboards-for-a-new-release-branch )
45
+ - [ \[ Continuously\] Monitor CI signal] ( #continuously-monitor-ci-signal )
46
+ - [ \[ Continuously\] Reduce the amount of flaky tests] ( #continuously-reduce-the-amount-of-flaky-tests )
47
+ - [ \[ Continuously\] Bug triage] ( #continuously-bug-triage )
47
48
48
49
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
49
50
@@ -155,6 +156,7 @@ This can be done by:
155
156
#### [ Repeatedly] Cut a release
156
157
157
158
1 . Ensure CI is stable before cutting the release (e.g. by checking with the CI manager)
159
+ Note: special attention should be given to image scan results, so we can avoid cutting a release with CVE or document known CVEs in release notes.
158
160
2 . Create and push the release tags to the GitHub repository:
159
161
``` bash
160
162
# Export the tag of the release to be cut, e.g.:
@@ -388,6 +390,8 @@ The goal of this task is to keep our tests running in CI stable.
388
390
1. Create an issue using an appropriate template (failing-test) in the Cluster API repository to surface the CI failure.
389
391
2. Identify if the issue is a known issue, new issue or a regression.
390
392
3. Mark the issue as ` release-blocking` if applicable.
393
+ 4. Triage periodic GitHub actions failures, with special attention to image scan results;
394
+ Eventually open issues as described above.
391
395
392
396
# ### [Continuously] Reduce the amount of flaky tests
393
397
0 commit comments