-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add option to specify which type of release to upgrade to (i.e. release/pre-release) #4532
Comments
Good idea. I think to add a checkbox to the settings to enable "notify on pre-releases" which is used once a update notification is received to either ignore the popup or to show it (as well as related UI updates like the update text in the footer). Would you mind to change the term capability to "option" or the like? I got first the impression you refer to the Capabilities (a feature we use to manage migration/compatibility of new features). |
Yes good point. I updated the wording. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still relevant. |
We recently started providing pre-release versions that are available a few days prior to an official release in the hopes of preventing unnecessary hotfixes after a release by allowing those that wish to try it out and provide feedback.
However, these pre-release versions are not notified/downloaded within the application and must be manually downloaded from Github. This means the user must rely on being notified of the pre-release through Keybase or by being subscribed to the repository. In addition, they must (hopefully) manually verify the downloaded files.
If we were to add the option to allow the user to specify which type of releases they want to upgrade to, that would allow them to be notified within the application and make the upgrade process much easier as it would handle the download and verification steps automatically. The biggest benefit may be that it potentially make more users try out the pre-release versions and provide early feedback.
The text was updated successfully, but these errors were encountered: