Andrea Frittoli

/lifecycle frozen

/hold

This seems very sudden to me, we just introduced remote resolution in the past release (v0.40) and we've had no experience using it in dogfooding or feedback from users that...

> Based on discussions around promoting features last week, I'm opting to skip the need for a `beta` flag and take remote resolution straight to `stable`. From the PR description:...

> @afrittoli as of today "promoted to stable" means to `v1beta1`, which is _beta_ anyway. I don't think we want to have 3 levels of `enable-api-fields` as it's gonna become...

> I prefer to pay the price in code duplication, generation, sharing, … than making the user pay it. If we need to have another reconciler specifically for a new...

Hello @leiyanggz - thank you for your contribution. Are you still interested in contributing this? I see the TEP is in the proposed state - did you hit any road...

Based on @imjasonh response, I will close this one. Feel free to re-open if required.

Thanks @JeromeJu - could you please add release notes? I know `v1` is not released yet, but I think it would good to have release notes still.

> We can probably add a cloud event response type behind a opt in flag? It sounds good, but I think it should be only for incoming CloudEvents.