You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/release/release-tasks.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -98,17 +98,17 @@ This comes down to changing occurrences of the old version to the new version, e
98
98
* v1beta1: `v1.0`, `v1.2`, `v1.3` (will change with each new release)
99
99
2. Update providers in `docker.yaml`:
100
100
1. Add a new `v1.3.0` entry.
101
-
2. Remove providers that are not used anymore (for `v1.4` we don't have to remove any).
101
+
2. Remove providers that are not used anymore in clusterctl upgrade tests.
102
102
3. Change `v1.3.99` to `v1.4.99`.
103
103
3. Adjust `metadata.yaml`'s:
104
104
1. Create a new `v1.3``metadata.yaml` (`test/e2e/data/shared/v1.3/metadata.yaml`) by copying
105
105
`test/e2e/data/shared/main/metadata.yaml`
106
106
2. Add the new release to the main `metadata.yaml` (`test/e2e/data/shared/main/metadata.yaml`).
107
-
3. Remove old `metadata.yaml`'s that are not used anymore (for `v1.4` we don't have to remove any).
107
+
3. Remove old `metadata.yaml`'s that are not used anymore in clusterctl upgrade tests.
108
108
4. Adjust cluster templates in `test/e2e/data/infrastructure-docker`:
109
109
1. Create a new `v1.3` folder. It should be created based on the `main` folder and only contain the templates
110
110
we use in the clusterctl upgrade tests (as of today `cluster-template` and `cluster-template-topology`).
111
-
2. Remove old folders that are not used anymore (for `v1.4` we don't have to remove any).
111
+
2. Remove old folders that are not used anymore in clusterctl upgrade tests.
112
112
5. Modify the test specs in `test/e2e/clusterctl_upgrade_test.go` (according to the versions we want to test described above).
113
113
Please note that both `InitWithKubernetesVersion` and `WorkloadKubernetesVersion` should be the highest mgmt cluster version supported by the respective Cluster API version.
114
114
2. Update `create-local-repository.py` and `tools/tilt-prepare/main.go`: `v1.3.99` => `v1.4.99`.
0 commit comments