github/confidential-containers
1
0
Fork 0
mirror of https://github.com/confidential-containers/confidential-containers.git synced 2025-10-21 15:31:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

release-check-list: flip the order of checkboxes and numbers

Browse Source 
Inverted the order of the checkboxes and numbers so that Github provides
a tracker of how many steps are done at the top of the issue.

Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com>
Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
This commit is contained in:
Wainer dos Santos Moschetta
2023-07-27 10:33:58 -03:00
committed by Tobin Feldman-Fitzthum
parent 4f69d4ea76
commit 99a84b7d1e
1 changed files with 23 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
.github/ISSUE_TEMPLATE/release-check-list.md vendored
View File

@@ -10,7 +10,7 @@ assignees: ''
## Code freeze
1. - [ ] Update Enclave CC to use the latest commit from image-rs
- [ ] 1. Update Enclave CC to use the latest commit from image-rs
* https://github.com/confidential-containers/enclave-cc/blob/main/src/enclave-agent/Cargo.toml
* Change the revision
@@ -18,7 +18,7 @@ assignees: ''
Note that you can point to your own fork here, so you don't actually do changes in the other projects
before making sure this step works as expected.
2. - [ ] Update Kata Containers to use the latest commit from image-rs, attestation-agent and td-shim
- [ ] 2. Update Kata Containers to use the latest commit from image-rs, attestation-agent and td-shim
* image-rs
* https://github.com/kata-containers/kata-containers/blob/CCv0/src/agent/Cargo.toml
@@ -30,10 +30,10 @@ assignees: ''
* https://github.com/kata-containers/kata-containers/blob/CCv0/versions.yaml
* Change the version
3. - [ ] Wait for kata-runtime-payload-ci to be successfully built
- [ ] 3. Wait for kata-runtime-payload-ci to be successfully built
* After the previous PR is merged wait for the kata-runtime-payload-ci (https://github.com/kata-containers/kata-containers/actions/workflows/cc-payload-after-push.yaml) has completed, so the latest kata-runtime-payload-ci contains the changes
4. - [ ] Check if there are new changes in the pre install payload script
- [ ] 4. Check if there are new changes in the pre install payload script
* https://github.com/confidential-containers/operator/tree/main/install/pre-install-payload
* The last commit there must match what's in the following files as preInstall / postUninstall image
@@ -42,7 +42,7 @@ assignees: ''
Note that for Kata Containers, we're looking for the newTag, below the quay.io/confidential-containers/container-engine-for-cc-payload image
* default: https://github.com/confidential-containers/operator/blob/main/config/samples/ccruntime/default/kustomization.yaml
5. - [ ] Ensure the Operator is using the latest CI builds and that the Operator tests are passsing
- [ ] 5. Ensure the Operator is using the latest CI builds and that the Operator tests are passsing
* Enclave CC:
* SIM: https://github.com/confidential-containers/operator/blob/main/config/samples/enclave-cc/sim/kustomization.yaml
@@ -53,18 +53,18 @@ assignees: ''
* peer-pods: https://github.com/confidential-containers/operator/blob/main/config/samples/ccruntime/peer-pods/kustomization.yaml
Note that we need the quay.io/confidential-containers/runtime-payload-ci registry and kata-containers-latest tag
6. - [ ] Update peer-pods with latest commits of kata-containers and attestation-agent and test it, following the [release candidate testing process](https://github.com/confidential-containers/cloud-api-adaptor/blob/main/docs/Release-Process.md#release-candidate-testing)
- [ ] 6. Update peer-pods with latest commits of kata-containers and attestation-agent and test it, following the [release candidate testing process](https://github.com/confidential-containers/cloud-api-adaptor/blob/main/docs/Release-Process.md#release-candidate-testing)
7. - [ ] Cut an attestation-service v<TARGET_RELEASE> and make images for AS and RVPS, if changes happened in the project.
- [ ] 7. Cut an attestation-service v<TARGET_RELEASE> and make images for AS and RVPS, if changes happened in the project.
* https://github.com/confidential-containers/attestation-service
* Cut a release (AS/RVPS images will be automatically built triggered by release)
8. - [ ] Cut a guest-components v<TARGET_RELEASE> release
- [ ] 8. Cut a guest-components v<TARGET_RELEASE> release
9. - [ ] Cut a td-shim v<TARGET_RELEASE> release, if changes happened in the project
- [ ] 9. Cut a td-shim v<TARGET_RELEASE> release, if changes happened in the project
10. - [ ] Update kbs to use the tagged attestation-service and guest-components, cut a release and make image
- [ ] 10. Update kbs to use the tagged attestation-service and guest-components, cut a release and make image
* https://github.com/confidential-containers/kbs/blob/main/src/api/Cargo.toml
* Change the revision for the `as-types` and `attestation-service` crates (both use `v<TARGET_RELEASE>`) and update the lock file
@@ -73,46 +73,46 @@ assignees: ''
* Cut a release
* kbs image will be automatically built triggered by release, so ensure that the [release workflow](https://github.com/confidential-containers/kbs/actions/workflows/release.yaml) ran successfully
11. - [ ] Update Enclave CC to use the released version of image-rs
- [ ] 11. Update Enclave CC to use the released version of image-rs
* redo step 3, but now using v<TARGET_RELEASE>
12. - [ ] Update Kata Containers to the latest released version of:
- [ ] 12. Update Kata Containers to the latest released version of:
* image-rs (redo step 4, but now using the v<TARGET_RELEASE>)
* attestation-agent (redo step 5, but now using the v<TARGET_RELEASE>)
* td-shim (redo step 6, but now using the v<TARGET_RELEASE>)
13. - [ ] Update the operator to use the images generated from the latest commit of both Kata Containers and Enclave CC
- [ ] 13. Update the operator to use the images generated from the latest commit of both Kata Containers and Enclave CC
* redo step 8, but now targetting the latest payload image generated for Kata Containers and Enclave CC
14. - [ ] Make sure all the operator tests are passing
- [ ] 14. Make sure all the operator tests are passing
15. - [ ] Cut an Enclave CC release
- [ ] 15. Cut an Enclave CC release
16. - [ ] Add a new Kata Containers tag
- [ ] 16. Add a new Kata Containers tag
17. - [ ] 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
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)
- [ ] 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
19. - [ ] 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
20. - [ ] Update the Operator version
- [ ] 20. Update the Operator version
* https://github.com/confidential-containers/operator/blob/main/config/release/kustomization.yaml#L7
21. - [ ] Cut an operator release
- [ ] 21. Cut an operator release
22. - [ ] Make sure to update the release notes and tag the confidential-containers repository
- [ ] 22. Make sure to update the release notes and tag the confidential-containers repository
* https://github.com/confidential-containers/documentation/tree/main/releases/v<TARGET_RELEASE>.md
23. - [ ] Poke Wainer Moschetta (@wainersm) to update the release to the OperatorHub
- [ ] 23. Poke Wainer Moschetta (@wainersm) to update the release to the OperatorHub