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

Slow rollout makes "Search for updates" button functionless #16854

Open
kghbln opened this issue Dec 1, 2020 · 4 comments
Open

Slow rollout makes "Search for updates" button functionless #16854

kghbln opened this issue Dec 1, 2020 · 4 comments
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.

Comments

@kghbln
Copy link

kghbln commented Dec 1, 2020

Refs
How to force detection of available updates?

Setup
Matomo 3.x and 4.x

Issue
The slow rollout make sure that not all users of Matomo get notifications about new versions at the same time. However it is not possible to override the slow rollout mechanism by clicking on the "Search for updates" button provided by Matomo. Thus the button is function-less.

Enhancement
It will be great if it is possible to override the slow rollout mechanism by manually triggering the search for a new version. This is even more important if published security vulnerabilities with existing outdated versions were addressed with a new release.

Bildschirmfoto vom 2020-12-01 18-53-44

@kghbln kghbln changed the title Slow rollout make "Search for updates" button functionless Slow rollout makes "Search for updates" button functionless Dec 1, 2020
@tsteur
Copy link
Member

tsteur commented Dec 1, 2020

Hi @kghbln the workaround be to change the release channel to the "beta" channel in the general settings as mentioned in the Matomo 4 changelog. This way you'll get the update immediately.

@tsteur tsteur closed this as completed Dec 1, 2020
@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label Dec 1, 2020
@kghbln
Copy link
Author

kghbln commented Dec 1, 2020

@tsteur Let me ask the other way around. What is the functionality of this button?

This is not about switching to beta or whatever, this is about checking for new versions regardless on which channel your are. Please also see the discussion I linked. I am not the only one here who thinks that there is an issue.

@tsteur
Copy link
Member

tsteur commented Dec 2, 2020

@kghbln we're only using this staged release for a major version upgrade so it's only a thing like every 3 years. If someone really wants to receive the update earlier then there is a workaround with changing the release channel temporarily. In all other cases it should be fine waiting for 1-2 weeks. If you're keen on getting the security fixes etc then there is a way with changing the release channel. The security issues have been fixed in github for many months and have been included in all the beta releases etc so if someone wanted them as quick as possible then I recommend using the beta channel anyway.

I'll reopen this issue in case we implement a force update check in the future. It be of course nice if you could force getting the update by clicking on it.

@tsteur tsteur reopened this Dec 2, 2020
@tsteur tsteur added c: Usability For issues that let users achieve a defined goal more effectively or efficiently. and removed answered For when a question was asked and we referred to forum or answered it. labels Dec 2, 2020
@tsteur tsteur added this to the Backlog (Help wanted) milestone Dec 2, 2020
@kghbln
Copy link
Author

kghbln commented Dec 2, 2020

Thanks for your insight.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.
Projects
None yet
Development

No branches or pull requests

2 participants