@@ -15,16 +15,16 @@ will:
1515 + generate the install.yaml for the release
1616 + create a [ GitHub release] ( https://github.com/project-codeflare/appwrapper/releases ) that contains the install.yaml
1717
18- 4 . To workaround back level go versions in ODH, we also maintain a
19- codeflare-releases branch. After making a release, create a branch
20- from the codeflare-release branch, merge main into the branch and
21- then submit a PR against the codeflare-release branch. After
22- CI passes, merge the PR and then tag the branch using a ` cf ` prefix
23- instead of a ` v ` . (eg v0.21.2 ==> cf0.21.2). After making this
24- tag, you can update the codeflare-operator, using the vX.Y.Z tag in
25- the Makefile and the cfX.Y.Z in the replace clause in codeflare's
26- go.mod.
27-
28- 5 . Update the kustomization.yaml files in MLBatch to refer to the new release:
18+ 4 . Update the kustomization.yaml files in MLBatch to refer to the new release:
2919 + setup.k8s-v1.27/appwrapper/kustomization.yaml
3020 + setup.k8s-v1.30/appwrapper/kustomization.yaml
21+
22+ 4 . To workaround back level go versions in ODH, we also maintain a
23+ codeflare-releases branch. After making a release, merge main
24+ into the codeflare-release branch creating a merge commit and
25+ push to the upstream codeflare-releases branch. After CI passes,
26+ tag the branch using a ` cf ` prefix instead of a ` v ` . (eg v0.21.2 ==> cf0.21.2).
27+
28+ 5 . You can update the codeflare-operator, using the vX.Y.Z tag in the Makefile
29+ and optionally the cfX.Y.Z in the replace clause in codeflare's go.mod if there
30+ is a difference in go levels between Kueue/AppWrapper and the codeflare-operator.
0 commit comments