Release cadence?

[fitzthum]

The CoCo release process no longer bumps the versions of all the subprojects. Should we formalize when we will cut releases of this repo?

[Xynnn007]

I might not get the point, so what do you think of we need?

[Xynnn007]

Oh. I might got your point.

Some personal ideas

• Based on previous 6-week frequency
• Everytime there is a big change upon API between guest-components and trustee -- some users of CoCo mentioned the newer API does not match the previous version API. Thus I think a good choice is to have a tag -- with the same tag the API will be compatible. Although API changing is not a good thing, but as CoCo is still under development, this could be acceptable, I think.

We have some e2e tests for kbs-client to interact with trustee

[fitzthum]

I think 6-weeks is a good starting point. We can do an additional release if we make any big API changes. I think we should probably try to cut a release ASAP. Maybe as soon as the secure execution stuff is merged?

[Xynnn007]

We might want confidential-containers/guest-components#576 to get merged to test SE.