k8s 1.7 corresponding release of client-go

[hongchaodeng]

k8s 1.7 is released.
When is client-go doing a release to match that?

[ericchiang]

cc @caesarxuchao who had some thoughts on this.

[caesarxuchao]

Because the pkg/api pkg/apis are all removed (for good), so we have breaking changes again, so it will be client-go release-4.0. I'll set it up. edit: they are removed in master, not 1.7, so it will affect only next release.

It's insane to bump the major version every quarter. I'll open another issue discussing how to enabling API tests and integration tests for client-go, and eventually decouple the release from kubernetes.

[lavalamp]

Why is it bad to increment the major version?

…

On Fri, Jun 30, 2017 at 11:38 AM, Chao Xu ***@***.***> wrote: Because the pkg/api pkg/apis are all removed (for good), so we have breaking changes again, so it will be client-go release-4.0. I'll set it up. It's insane to bump the major version every quarter. I'll open another issue discussing how to enabling API tests and integration tests for client-go, and eventually decouple the release from kubernetes. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#231 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnglnM4h4SAgYN1UdR2HWGLwRc8gfC7ks5sJUCqgaJpZM4OK33x> .

[caesarxuchao]

We do not back-port new API groups or new features like leader election across major releases. Users who want to use these features need to upgrade, their life will be easier if we don't bump the major version often.

[tamalsaha]

We do now back-port new API groups or new features like leader election across major releases.

Do you mind elaborating on that? We write operators for Kubernetes. Dealing with breaking changes with every release of Kubernetes is a major headache for us.

[joshwget]

Because the pkg/api pkg/apis are all removed (for good), so we have breaking changes again, so it will be client-go release-4.0. I'll set it up.

Isn't this code imported in various places in 1.7? For those looking for a client-go release to use when importing code from Kubernetes 1.7 this wouldn't work.

[caesarxuchao]

@joshwget sorry, i took that back. pkg/api and pkg/apis are still there in kubernetes/release-1.7, so they will be in the client-go branch that tracks kubernetes/release-1.7.

[joshwget]

Awesome, thanks for confirming that.

[lavalamp]

Users who want to use these features need to upgrade, their life will be easier if we don't bump the major version often.

I just want to point out that users who want new features and also don't want to upgrade want a logically impossible thing. ;)

[caesarxuchao]

I created the release-4.0 branch. Now i need to manually fill out the CHANGELOG, then release the v4.0.0.

[caesarxuchao]

I made the v4.0.0-beta.0 tag. I'll gvie the beta.0 one week time to soak and create v4.0.0 tag next week.

[svInfra17]

@caesarxuchao , is v4.0.0-beta.0 ready for v4.0.0 ?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[nikhita]

This is fixed now and the README and CHANGELOG are updated.

Closing.
/close