When creating releases we should pin the version of source.tar.gz used in the deploy.sh

[jlewi]

If you pull deploy.sh from a release branch, by default you should get the source.tar.gz associated with that branch. But that's not what currently happens because the default version is master.

As part of a release we should update deploy.sh so we get the source repo at the same version as deploy.sh

kubeflow/website#96 - Using our website we can now create redirects to github URLs.

So we could create links like

https://kubeflow.org/version/0.2.2/source.tar.gz

This way we can just redirect that link to different RCs without having to update deploy.sh.

[jlewi]

I fixed this on the 0.2.2 branch.

At master we should upload download.sh and update the release instructions.

[jlewi]

With the latest config scripts we now use download.sh
https://github.com/kubeflow/kubeflow/blob/master/scripts/download.sh

All the files downloaded will be at a single commit.

We still have the problem that download.sh might be pointing by default at a different commit. We can potentially fix that by redirecting to download.sh from
https://kubeflow.org
so that we can potentially reference a different version of the script.

At any rate closing this issue since we don't use deploy.sh