Release notes for operator-sdk version upgrade epic

[Jaanki]

submariner-io/enhancements#81

Signed-off-by: Janki Chhatbar [email protected]

[submariner-bot]

🤖 Created branch: z_pr2323/Jaanki/sdk_upgrade_rn
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

[skitt]

I thought we’d said the Operator SDK changes didn’t need release notes, since they’re not user-visible. Has that changed?

[Jaanki]

I wasn't aware of this decision. Anyways, I think the path change for APIs should be mentioned. It could be used by other projects.

[skitt]

Suggested change

	* operator-sdk version is upgraded to 1.23.0.
	* Submariner-operator APIs are converted to single-group. Meaning, API definitions can now be found under `api/`.
	* The project was rebuilt using Operator SDK version 1.23.0.
	* The operator APIs have been converted to single-group; projects depending on these will need to
	replace `github.com/submariner-io/submariner-operator/api/submariner/v1alpha1` with
	`github.com/submariner-io/submariner-operator/api/v1alpha1` in their imports.

[tpantelis]

I wasn't aware of this decision. Anyways, I think the path change for APIs should be mentioned. It could be used by other projects.

Fair enough, let’s describe the impact explicitly.

Also discussing this on slack. We've stated and agreed in the past that RNs are for end users. A Go API change is not for end users. We've many Go API changes in the past sans RN. Let's stay consistent.

[tpantelis]

Also discussing this on slack. We've stated and agreed in the past that RNs are for end users. A Go API change is not for end users. We've many Go API changes in the past sans RN. Let's stay consistent.

As a follow-up, to notify possible users of the submariner-operator project of the API change, we could add a note to the project release tag once that's created.

[submariner-bot]

🤖 Closed branches: [z_pr2323/Jaanki/sdk_upgrade_rn]