When this is merged, the release script will still be failing at the "sync to Docker Hub" step, since at this moment the repos on Docker Hub are automated builds, which don't accept direct pushes. We'll need to migrate those to normal repositories.
After that, the next step is running this process on Travis, triggered by a tag (say release-1.4.0, to not confuse the build triggers in Quay.io)
This is a better implementation of https://github.com/openzipkin/docker-zipkin/pull/38, see the description of that PR for a detailed discussion of the trade-offs behind this.
When this is merged, the release script will still be failing at the "sync to Docker Hub" step, since at this moment the repos on Docker Hub are automated builds, which don't accept direct pushes. We'll need to migrate those to normal repositories.
After that, the next step is running this process on Travis, triggered by a tag (say
release-1.4.0, to not confuse the build triggers in Quay.io)