-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
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
Inconsistent download pages #855
Comments
This was discussed on the TSC more recently, and we came to a conclusion about how we'd like to fix this. The fix needs to be written here https://github.com/zowe/zowe.github.io This currently happens for the convenience build download. |
Note: the verification file referenced in the post_download page already exists for all the download types, you can find it at https://zowe.jfrog.io/zowe/list/libs-release-local/org/zowe/2.9.0/, substituting version & file. |
It's been added for client side and the issue belongs to https://github.com/zowe/zowe.github.io |
Thanks @balhar-jakub for working on this. |
When you download something on https://www.zowe.org/download.html
The action that happens after the download varies by which thing you download.
Some downloads redirect the webpage to a docs.zowe.org page which explains how to install them.
Others redirect the webpage to a zowe.org page which explains how to verify the authenticity of the download.
But, we should do both, always!
https://zowe.jfrog.io/artifactory/list/libs-release-local/org/zowe/2.2.0/ contains the hash needed to verify any of our zowe downloads.
But only the pax option sends you to this page https://www.zowe.org/post_download.html?version=2.2.0 explaining how to get the hash file, and how to use it.
The page seems specific to .pax, but the instructions can be done on any of the download types!
And, if you end up at docs.zowe.org instead of this page, docs.zowe.org doesnt have these instructions so you can't learn how to verify a download with the other download types
I think the website should be changed to either
or
The text was updated successfully, but these errors were encountered: