-
Notifications
You must be signed in to change notification settings - Fork 481
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
Improve UX around removed release binaries #672
Comments
I think I'd prefer just changing everything to say,
Would you find that to be a satisfactory solution, @jlopp? Does anyone have any objection to doing that on this website? Does anyone have an opinion about whether I should upstream that change to bitcoin/bitcoin for future release notes as distributed in other places than just this website? |
Sounds good to me. |
I think the kind of security issues that warrant removing releases are rare enough that we can just consider removing the links for those versions, instead. And I think it's fine to keep direct links otherwise. But no strong opinion. |
I like all of #672 (comment), |
I needed to run some old versions of Core for backwards compatibility testing with a project and noticed that a number of the Release Announcement pages have broken links. For example, https://bitcoincore.org/en/releases/0.16.0/ links to https://bitcoincore.org/bin/bitcoin-core-0.16.0/
Clearly they have been removed for security reasons #605
However, this is not obvious or user friendly. I'd suggest changing the release announcement pages to be more clear and to link to the secure minor version of the corresponding release.
The text was updated successfully, but these errors were encountered: