Skip to content
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

Open
jlopp opened this issue Sep 21, 2019 · 5 comments
Open

Improve UX around removed release binaries #672

jlopp opened this issue Sep 21, 2019 · 5 comments

Comments

@jlopp
Copy link
Contributor

jlopp commented Sep 21, 2019

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.

@harding
Copy link
Contributor

harding commented Sep 22, 2019

I think I'd prefer just changing everything to say,

The latest version of Bitcoin Core is always available from https://bitcoincore.org/en/download/

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?

@jlopp
Copy link
Contributor Author

jlopp commented Sep 22, 2019

Sounds good to me.

@laanwj
Copy link
Member

laanwj commented Nov 8, 2019

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.

@l33d4n
Copy link

l33d4n commented Aug 29, 2020

Anyone have a suggestion how to solve this issue?
What do you think about this kind of change?

image

@katesalazar
Copy link
Contributor

I like all of #672 (comment),
#672 (comment), #672 (comment).
Might code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants