| Summary: | Auto-Update | ||
|---|---|---|---|
| Product: | [Applications] krita | Reporter: | X-Raym <extremraym> |
| Component: | General | Assignee: | Krita Bugs <krita-bugs-null> |
| Status: | RESOLVED LATER | ||
| Severity: | wishlist | CC: | halla, scottpetrovic, tamtamy.tymona |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
X-Raym
2016-05-20 12:28:37 UTC
Over IRC we discussed this a bit. It might be a good idea to make this an opt-in to even check. Some people seemed a bit worried that Krita might be spying on everyone if we do this. Two ways we could do this is to just alert the person when there is a new version available and give them a link. This would take a little time. The second solution would be to auto-update kind of like how Google Chrome does it without needing to manually go to the site. This would take longer to do. The one negative potential for this background update is if we introduce a build that would have bugs that would break things. We don't have much of a QA team, so this could potentially give people problems. They could always opt-out if they don't want to be on it. Sure, the Chrome kind of autoupdate (notifications + click to download following by auto install + relaunching the software) would be the more handy solution. To prevent unexpected bug introduction, the user could choose in preference if he want to be warn for stable version only or also for betas. If you thing there is too much risk for a beta user to have unexpected bugs, then you could have a rollback solution : the previous version is not deleted when you update to the new one. But this may be a bit complicated, and there is other priorities for sure. Anyway, thanks for your answer and support ! Note that if you get Krita on Steam, you already get automatic updates (though you need to enable the beta channel for now, that's going to change after we release 3.0). I'm actually not sure I want to invest time in setting up another update mechanism, so this is definitely a patches are welcome, if someone volunteers to be a maintainer kind of thing. The situation in the time of writing this comment: - there is a small notification on the Welcome Screen that an update is available. - when you click the notification (it's underlined, signaling it's a link), it brings you to the blog post on krita.org about the release so the user can download a new version. Still not completely automatic, but that's an improvement. Moreover automatic updates are possible both on Steam, Windows Store, Google Play and Linux repositories. autoupdates have been implemented for krita5 for appimages on Linux. For the rest, steam, windows store, snap, krita lime and flatpak autoupdate. We don't autoupdate on macos, because we're not in the macos store (where Krita would be a paid option), because we're not happy with krita on macos as it is. When we are happy with that, krita will be in the store. The krita.org downloads for macos and windows won't get autoupdating. |