-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Release] Check list for v0.5.0 #80
Comments
I believe the following PRs need to be tested, approved and merged to start the release:
tests:
ssh-demo: I'm current running CI of all those PRs together (using depends-on) in: |
Also, this release also includes KBS/AS. We might need the following steps:
PR for docker-compose: |
@Xynnn007 where is the release automation for those container images? Tagging and syncing up more dependencies and repositories is problematic and unsustainable. This needs a better solution. |
Yes, you're right. Now we do not have one. Do you have any examples or suggestions? I can start with this, probably after v0.5.0 |
Hi @jepio , All those PR are closed now. Can we start the freeze process? What can I do to help? |
@wainersm, what about start with items from 1-5? |
Good idea. Edited the description, put my name on those items. |
This is a summary of steps 1-6:
The steps 7 and 8 can be carried out as soon as https://github.com/kata-containers/kata-containers/actions/runs/4693722127 finishes, that is going to generate the new runtime payload (https://quay.io/repository/confidential-containers/runtime-payload-ci?tab=tags) for the operator. @larrydewey |
Items 7 and 8 are covered here: confidential-containers/operator#200 |
ocicrypt-rs release: https://github.com/confidential-containers/ocicrypt-rs/releases/tag/v0.5.0 |
attestation-agent release: https://github.com/confidential-containers/attestation-agent/releases/tag/v0.5.0 |
image-rs release with up-to-date tags: https://github.com/confidential-containers/image-rs/releases/tag/v0.5.0 |
Second try: https://github.com/confidential-containers/image-rs/releases/tag/v0.5.1 |
Enclave CC release was cut: https://github.com/confidential-containers/enclave-cc/releases/tag/v0.5.0 |
Kata Containers tag has been created: https://github.com/kata-containers/kata-containers/releases/tag/CC-0.5.0 |
https://github.com/confidential-containers/documentation/blob/main/releases/v0.5.0.md was updated 2 weeks ago. |
@jensfr, the only bit missing from the checklist is adding the release to the OperatorHub. |
yep, I'll do that |
Docs are done for v0.5.0. I am holding off on tagging the docs until Monday so that we can change the link to the CAA README to point to main rather than staging. |
PR for operatorhub is merged |
Documentation tagged now. |
v0.5.0
Code freeze
- 1. Update image-rs to use the latest commit from ocicrypt-rs (@wainersm)
- 2. Update image-rs to use the latest commit from attestation-agent (@wainersm)
- 3. Update Enclave CC to use the latest commit from image-rs (@wainersm)
- 4. Update Kata Containers to use the latest commit from image-rs (@wainersm)
- 5. Update Kata Containers to use the latest attestation-agent (@wainersm)
- 6. Update Kata Containers to use the latest td-shim (@wainersm)
- 7. Check if there are new changes in the pre install payload script
- 8. Ensure the Operator is using the latest CI builds and that the Operator tests are passsing
- 9. Cut an ocicrypt-rs v<TARGET_RELEASE> release, if changes happened in the project
- 10. Cut an attestation-agent v<TARGET_RELEASE>, if changes happened in the project
- 11. Cut an image-rs v<TARGET_RELEASE> release, using the latest release of:
- 12. Cut a td-shim v<TARGET_RELEASE> release, if changes happened in the project
- 13. Update Enclave CC to use the released version of image-rs
- 14. Update Kata Containers to the latest released version of:
- 15. Update the operator to use the images generated from the latest commit of both Kata Containers and Enclave CC
- 16. Make sure all the operator tests are passing
- 17. Cut an Enclave CC release
- 18. Add a new Kata Containers tag
Release
- 19. Update the operator to use the release tags coming from Enclave CC and Kata Containers
- 20. Update the Operator version
- 21. Cut an operator release
- 22. Make sure to update the release notes
- 23. Poke Jens Freimann (jfreiman@redhat.com) to update the release to the OperatorHub
The text was updated successfully, but these errors were encountered: