Found a line here that makes no sense.

Have working instructions for running Kubernetes 1.10 on top of
minikube 0.28.0 - including a workaround for non default profiles.

Since Agones works fine on k8s 1.10, figured it was worth making the move.

Implemented workerqueue for node modifications in the
PortAllocator, so that if the master happens to go
down, then the operations the PortAllocator has to do
to keep things in check will retry and result in a
correct state.

Closes #60

- (Conflict merge) Update Helm App Version
- update doc as requested

Implement grpc-gateway in front of the gRPC based sdk-server, so that
it can be access via HTTP+JSON.

This includes documentation and a swagger/openapi specificiation.

This also has been implemented such that the sdk-server is still a single
binary, and as such, the HTTP+JSON interface can still be used for local
development.

Closes #240

Some more tutorials to help people get started.

Missed that this should be 0.3.0

This should hopefully fix these tests.

There was a race condition in the original
implementation. This fixes that issue!

(and makes the code cleaner!)

Trying to stop timeouts :/

This also replaces the C++ build image we have from the gRPC docker hub,
with one that we manage ourselves, since getting updates in a timely
matter was getting difficult.

The C++ base will likely go away once the transition to REST based SDK,
so the base may end up going away.

This is prerequisite for #240

Just keeping up with updates.

I think this will stop this test being flakey.

I believe this shoud fix this flakey test

Realised that all the new Rust SDK code
didn't have the Apache licence applied.

This applies the licence.

Make it clearer to download the release archive
from releases, rather than an implied `git checkout`

Closes #248

- Include Rust in the list of SDKs
- Also put a development warning on the SDK

This should make Cloud Builder faster
- Request an 8 core machine
- Move the test and build steps to be parralel.

Noticed that this library wasn't locked to a version,
so when I attempt to regen the code, I got some incompatible
code.

This fixes things.

Incrementing the base version post release.

Updates to docs, Changelog, etc for 0.2.0
release.

Let me know if you don't think this is actually
useful, but figured it might be a good resource
for some people?

This PR includes:
- small fixes to the release process that came up
  during the last release
- Adding links to the release process from the main README
- Including a release calendar that people can see.

Now we're in feature freeze, move install back to 0.2.0

Includes and updated Changelog, update the install.yaml
to rc version, and updates for the docs for release.

also update build documentation and move variable next to target

Previously we only kept the C++ build artifacts for each build and
release, which (if my understanding of C++ is correct - which I don't
think it was a while ago) is relatively useless, unless you are on the
same OS, compiler etc.

So here we are taking a zip of the src, and keeping it, pushing it to
Cloud Storage when a PR is made, and also making sure it's in the
releases folder on release.

Realised there were a couple of steps missing
from the release checklist.

This PR does two things:
1) Ensure the built images always have the release
 registry
2) Ensure the release branch is pushed to upstream,
 rather than to a forked origin.

Moved the installation documentation into the `install` directory
and on release, zip up the install instructions and yaml files
such that users can download and use them.

Added missing "\" at the end of command options.

Semver should have 3 digits, so we
should be releasing 0.2.0 next.