Release: Update payloads for v0.10.0

[niteeshkd]

No description provided.

[niteeshkd]

@portersrc @wainersm @fitzthum

[stevenhorsman]

LGTM. Thanks @niteeshkd!

[portersrc]

Looks OK to me. I sanity checked it by comparing against the same step for v0.9.0 here.

[fitzthum]

There still seems to be an issue with the kata version

[ldoktor]

It generally looks good, there is the v3.9.0 vs. 3.9.0 issue introduced in the 2nd commit and fixed in the 3rd one which needs to be corrected (so changes work separately).

One more thing I noticed is that there are still a couple of 3.9.0 entries here and there, shouldn't these be tackled together? {Makefile,config/manager/kustomization.yaml,config/manifests/bases/cc-operator.clusterserviceversion.yaml,bundle/manifests/cc-operator.clusterserviceversion.yaml}

[portersrc]

One more thing I noticed is that there are still a couple of 3.9.0 entries here and there, shouldn't these be tackled together?

I looked at the files you pointed to, and I guess you mean the 0.9.0 entries (i.e. some lingering, hard-coded coco version numbers)? This is a good catch. I see @wainersm was modifying these in the past -- looks related to operator hub. Is now the time to fold those manual steps into this release process, or are things still too much in flux and requiring extra effort each release?

Edit: This is Step 8 for us currently.

[fitzthum]

LGTM

[fitzthum]

Is now the time to fold those manual steps into this release process, or are things still too much in flux and requiring extra effort each release?

We have treated these as a later step in the past.

[mythi]

we did some manual testing too and seems working

[wainersm]

One more thing I noticed is that there are still a couple of 3.9.0 entries here and there, shouldn't these be tackled together?

I looked at the files you pointed to, and I guess you mean the 0.9.0 entries (i.e. some lingering, hard-coded coco version numbers)? This is a good catch. I see @wainersm was modifying these in the past -- looks related to operator hub. Is now the time to fold those manual steps into this release process, or are things still too much in flux and requiring extra effort each release?

Yes, those are the changes required for publishing the released operator in operator hub. The instructions are in here but I think it's a good idea to merge the steps into this doc, all in all, it's part of the release.

I don't know if step 8 could also be done simultaneously with step 5 (this). The bundle generated bundle files will point to the built operator image (quay.io/confidential-containers/operator:v${TARGET_RELEASE}). I don't know if the tool that build the bundle will check the existence of the image, if yes then step 8 should be done after the release.

For 0.10.0 release, maybe let's not change the flow.

Edit: This is Step 8 for us currently.

[fitzthum]

I guess there is a nonzero chance of v0.10.1 so I will wait to tag the repo.