We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Consistently name release artifacts.
kubeflow-
v
Example: Latest release asset is named v0.3.5, but unpacked folder is named kubeflow-0.3.5:
v0.3.5
kubeflow-0.3.5
$ wget https://github.com/kubeflow/kubeflow/archive/v0.3.5.tar.gz $ tar -xvf v0.3.5.tar.gz $ ls kubeflow-0.3.5
The text was updated successfully, but these errors were encountered:
I'm not sure how much control we have here.
I think the name "v0.3.5" is based on the release tag.
The tarball is autogenerated from the source tree as well by GitHub.
Sorry, something went wrong.
Oh right - because we're not generating binaries, this is an automated GH thing. Consistency across all of GH makes it less of an issue.
No branches or pull requests
Consistently name release artifacts.
kubeflow-
to archive name. This makes it easier to identify the source of the downloaded file.v
from version in unpacked artifact. This is consistent with version tags in the repo.Example:
Latest release asset is named
v0.3.5
, but unpacked folder is namedkubeflow-0.3.5
:The text was updated successfully, but these errors were encountered: