From f51c7faa4908e71979e90703554cf9432a702096 Mon Sep 17 00:00:00 2001 From: Wainer dos Santos Moschetta Date: Wed, 26 Jul 2023 14:11:48 -0300 Subject: [PATCH] release-check-list: move step 8 below to 9 Moved the step 8 ("Update kbs to use the latest commit ...") below to step 9 ("Cut a guest-components ...") because the kbs depend on guest-components, therefore, the later should be tagged *before* the former. Signed-off-by: Wainer dos Santos Moschetta --- .github/ISSUE_TEMPLATE/release-check-list.md | 23 ++++++++++---------- 1 file changed, 11 insertions(+), 12 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release-check-list.md b/.github/ISSUE_TEMPLATE/release-check-list.md index aab5fef..3452449 100644 --- a/.github/ISSUE_TEMPLATE/release-check-list.md +++ b/.github/ISSUE_TEMPLATE/release-check-list.md @@ -60,7 +60,11 @@ assignees: '' * https://github.com/confidential-containers/attestation-service * Cut a release (AS/RVPS images will be automatically built triggered by release) -8. - [ ] Update kbs to use the latest commit from attestation-service, cut a release and make image +8. - [ ] Cut a guest-components v release + +9. - [ ] Cut a td-shim v release, if changes happened in the project + +10. - [ ] Update kbs to use the latest commit from attestation-service, cut a release and make image * https://github.com/confidential-containers/kbs/blob/main/src/api_server/Cargo.toml * Change the revision for the following crates (both use `v`) @@ -68,10 +72,6 @@ assignees: '' * `attestation-service` * Cut a release (kbs image will be automatically built triggered by release) -9. - [ ] Cut a guest-components v release - -10. - [ ] Cut a td-shim v release, if changes happened in the project - 11. - [ ] Update Enclave CC to use the released version of image-rs * redo step 3, but now using v @@ -90,26 +90,25 @@ assignees: '' 15. - [ ] Cut an Enclave CC release -17. - [ ] Add a new Kata Containers tag +16. - [ ] Add a new Kata Containers tag - -18. - [ ] Wait for release kata-runtime-payload to be successfully built +17. - [ ] Wait for release kata-runtime-payload to be successfully built * After the Kata tag is created wait for (https://github.com/kata-containers/kata-containers/actions/workflows/cc-payload.yaml) to be successfully completed, so the latest commit kata-runtime-payload for the release is created -19. - [ ] Update peer pods to use the release versions and then cut a release following the [documented flow](https://github.com/confidential-containers/cloud-api-adaptor/blob/main/docs/Release-Process.md#cutting-releases) +18. - [ ] Update peer pods to use the release versions and then cut a release following the [documented flow](https://github.com/confidential-containers/cloud-api-adaptor/blob/main/docs/Release-Process.md#cutting-releases) ## Release -20. - [ ] Update the operator to use the release tags coming from Enclave CC and Kata Containers +19. - [ ] Update the operator to use the release tags coming from Enclave CC and Kata Containers * redo step 8, but now targeting the latest release of the payload image generated for Kata Containers eand Enclave CC -21. - [ ] Update the Operator version +20. - [ ] Update the Operator version * https://github.com/confidential-containers/operator/blob/main/config/release/kustomization.yaml#L7 -22. - [ ] Cut an operator release +21. - [ ] Cut an operator release 22. - [ ] Make sure to update the release notes and tag the confidential-containers repository