New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binary release cadence #208

Closed
alexellis opened this Issue Jan 10, 2019 · 6 comments

Comments

Projects
4 participants
@alexellis
Copy link

alexellis commented Jan 10, 2019

Hi folks,

I wrote a blog post on the heels of KubeCon Seattle explaining what KinD is and how it can be used for testing with Kubernetes. I wanted to write a follow-up but wasn't sure if go get is still the preferred installation method?

There is a binary 0.1 release but it looks out of date to me vs. master (I may be wrong)

What would you recommend here? It would be ideal if people didn't need go as a pre-req - especially if testing on a minimal VM.

Thanks 👍

Alex

@BenTheElder

This comment has been minimized.

Copy link
Member

BenTheElder commented Jan 10, 2019

/assign

I've been slightly hesitant to publish binaries I know I'll outright break compatibility with, but that should clear up as we finish fleshing out multi-node.

I want to make another change or two to the v1alpha2 API today and then get another release out.

The overall release cadence should pick up, and the intention is to stop making breaking changes if at all possible by the Kubernetes 1.14 release.

@BenTheElder

This comment has been minimized.

Copy link
Member

BenTheElder commented Jan 11, 2019

/priority important-soon

@BenTheElder BenTheElder added this to To do in 1.0 via automation Jan 11, 2019

@BenTheElder BenTheElder added this to the 1.0 milestone Jan 11, 2019

@BenTheElder

This comment has been minimized.

Copy link
Member

BenTheElder commented Jan 11, 2019

I want to get a release in early next week, I'm unhappy with the fact that the current mid-refactor config API is not fully respected by the implementation in some known ways, I'd like to get that patched before releasing again, but not much more since we already have some fairly substantial changes since the last alpha.

@luxas

This comment has been minimized.

Copy link

luxas commented Jan 15, 2019

You can always do an intermediate 0.1.0 release or something. I'd advocate for releasing fairly often while things change much, before starting to talk about stability. This also overlaps with k8s.io/component-base as said, and I hope that will become more stable over the coming weeks as well.

@BenTheElder

This comment has been minimized.

Copy link
Member

BenTheElder commented Jan 15, 2019

1.0 automation moved this from To do to Done Jan 16, 2019

@BenTheElder

This comment has been minimized.

Copy link
Member

BenTheElder commented Jan 16, 2019

Binaries are now up at https://github.com/kubernetes-sigs/kind/releases/tag/0.1.0, we will strive to release more often going forward, this was quite a large release. 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment