v0.10.30 doesn't show upgrade button for v0.11.0 #1680
Labels
bug
A problem with current functionality, as opposed to missing functionality (enhancement)
frozen-due-to-age
Issues closed and untouched for a long time, together with being locked for discussion
Comments
calmh
added
the
bug
|
I am sure there are lots of users like me who are GUI-centric, and a last version 0.10.31 with a big button to upgrade to v0.11.0 will be appreciated. |
|
Yes, it'll be there. As it is, most users probably won't know there is an upgrade available. |
|
👍 |
1 similar comment
|
+1 |
|
This requires some finessing... v0.10 only checks the topmost non-beta release, so we need to let a v0.10 release be the latest for a while to get older v0.10 clients on board. v0.11 is smarter and actually looks for the highest version among the most recent releases. So probably we want to wait for v0.11.1, then release v0.11.1 tightly followed by v0.10.31, then let it hover there for a week or so. The downside is that the "latest release" links will point to v0.10.31. |
|
(Merged into v0.10) |
st-review
added
the
frozen-due-to-age
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
syncthing -upgradeworks, but the button should be shown? Perhaps with a different note or color or something as it's a major upgrade. We should probably get this out as a last maintenance release on v0.10.The text was updated successfully, but these errors were encountered: