From 285f321d52eff535fdeff0c6cf88af89172a1f19 Mon Sep 17 00:00:00 2001 From: David Grove Date: Sun, 15 Dec 2024 14:54:09 -0500 Subject: [PATCH] tweak release docs again --- docs/release_instructions.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/release_instructions.md b/docs/release_instructions.md index cf3208c..0cc7024 100644 --- a/docs/release_instructions.md +++ b/docs/release_instructions.md @@ -15,16 +15,16 @@ will: + generate the install.yaml for the release + create a [GitHub release](https://github.com/project-codeflare/appwrapper/releases) that contains the install.yaml -4. To workaround back level go versions in ODH, we also maintain a - codeflare-releases branch. After making a release, create a branch - from the codeflare-release branch, merge main into the branch and - then submit a PR against the codeflare-release branch. After - CI passes, merge the PR and then tag the branch using a `cf` prefix - instead of a `v`. (eg v0.21.2 ==> cf0.21.2). After making this - tag, you can update the codeflare-operator, using the vX.Y.Z tag in - the Makefile and the cfX.Y.Z in the replace clause in codeflare's - go.mod. - -5. Update the kustomization.yaml files in MLBatch to refer to the new release: +4. Update the kustomization.yaml files in MLBatch to refer to the new release: + setup.k8s-v1.27/appwrapper/kustomization.yaml + setup.k8s-v1.30/appwrapper/kustomization.yaml + +4. To workaround back level go versions in ODH, we also maintain a + codeflare-releases branch. After making a release, merge main + into the codeflare-release branch creating a merge commit and + push to the upstream codeflare-releases branch. After CI passes, + tag the branch using a `cf` prefix instead of a `v`. (eg v0.21.2 ==> cf0.21.2). + +5. You can update the codeflare-operator, using the vX.Y.Z tag in the Makefile + and optionally the cfX.Y.Z in the replace clause in codeflare's go.mod if there + is a difference in go levels between Kueue/AppWrapper and the codeflare-operator.