Release 2.0.0 planning

[davidgamero]

proposal to release a client version 2.0.0-rc1 to gather initial feedback as the next release will the the first after full migration to undici from node-fetch

need someone with perms once we are aligned on plan to trigger workflows

k8s v1.36 is out, and we don't have a version for k8s v1.35 release yet.

proposing an rc generated on k8s v1.35, then a full release of client v2.0.0 (barring any major rc issues) before advancing to a k8s v1.36 compatible version (client v2.1.0) in the future.

looking for input to move forward

ref #2650

@mstruebing @cjihrig @brendandburns

[cjihrig]

This seems like a fine plan to me.

need someone with perms once we are aligned on plan to trigger workflows

You've been doing a ton of work lately. Maybe you should be onboarded as a maintainer again?

[brendandburns]

Works for me.

[mstruebing]

Sounds good.
I think everyone can do releases.

[davidgamero]

sure i've opened kubernetes/org#6369 to onboard