Release version 0.1.0 about minikube

[dlorenc]

Integration tests are passing at 7370924

If there are no objections I'll cut a release here tomorrow.

[luxas]

Remember to bump version in version.go before cutting the release

[luxas]

At least #126 should be in the first release, and #119 would be a nice to have.

[luxas]

Yes, now only a version bump in the Makefile should be done before cutting

[dlorenc]

Released here: https://github.com/kubernetes/minikube/releases/tag/v0.1

[luxas]

@dlorenc Why wasn't the version updated?
The released binary on github now outputs the wrong version which could be confusing for users:

$ minikube version
minikube version: v0.0.1

You might want to update the binaries...

[luxas]

I would also suggest always using vX.Y.Z version numbers.

If you feel you have time, you might want to update the version number, re-tag with v0.1.0 and upload new binaries. That's just a suggestion, feel free to ignore it for this time :)

[dlorenc]

Ah sorry, I meant to call this 0.0.1, to match the github tag/release. Maybe I can just rename the release to match that. I'll play with it tomorrow.

[luxas]

Okay, but I think the recommended starting version is v0.1.0, and IMO we should use that
e.g. dashboard did this in a good way: https://github.com/kubernetes/dashboard/releases/tag/v0.1.0

We've stated everywhere that the initial dev release will be 0.1, which equals v0.1.0 (not v0.0.1)

I think you should remove the tag v0.1, send a pr that bumps to v0.1.0, rebuild the binaries, tag it v0.1.0, push and click New Release in Github, mark it pre-release and paste back what you've already written in release notes.

[dlorenc]

Sure, sent #131

[dlorenc]

Released here: https://github.com/kubernetes/minikube/releases/tag/v0.1.0

[luxas]

Great! Thanks.