-
-
Notifications
You must be signed in to change notification settings - Fork 215
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
Upgrade process lacks feedback #2016
Comments
Hi, Personally, I think that a first step towards improvement would be to make for the upgrade process to be proactive instead of reactive. See, now, an update can come in "at any time" and the user is only able to tell that from once something doesn't work as expected (lags, downtime, ...). Cheers, Thomas |
Well, you can now hold snap refreshes indefinitely which kind of fits your use-case, doesn't it? |
Hi @pachulo - yep, thanks. I know. If I switch to hold back updates... (until I have time to take care) how will I know that there IS an update at all? Is there a way to have a kind of notification/email, you name it, that tells me "dude, there's an update you'll need to take care of"? At the moment, I need to intentionally LOOK for it. Nextcloud's internal update checks won't probably fit because what they publish doesn't fit to the snap update availability, right? So that leaves me with having to check snap updates on-demand (meaning: whenever it comes to my mind to check for it). Cheers, Thomas |
Not that I know @pawlowskatze . But I guess it won't be very difficult to craft a script to compare the installed snap version with the one available in |
The snap upgrade process is frustratingly opaque. It looks like Nextcloud is down for however long it takes to complete the upgrade. This should be far more user-friendly, at least showing some sort of maintenance mode screen so it's clear WHY it's down.
The text was updated successfully, but these errors were encountered: