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

Display a changelog after updating #4509

Closed
1 task done
vordenken opened this issue Sep 11, 2020 · 2 comments
Closed
1 task done

Display a changelog after updating #4509

vordenken opened this issue Sep 11, 2020 · 2 comments

Comments

@vordenken
Copy link

  • I have searched open and closed issues for duplicates


Feature Request regarding updates

After updating signal desktop to a newer version through the built in updater, there should be a changelog displayed after the update is successfully installed. Many average users probably don't know where to look for a changelog if there are interested and it shows users that there is progress. Also maybe a feature got added and people dont know it because its hidden/ not obvious to use.

Platform Info

Signal Version:
v1.36.1

Operating System:
macOS 10.15.6

@yb66
Copy link

yb66 commented Dec 19, 2020

Perhaps this feature could be extended to make the whole project, how shall we say, more hospitable towards users that might want this information or to control the update process further (i.e. at all):

  • Add a changelog file to the source (the update I did today has one entirely unhelpful line). I suggest the Keep A Changelog format.
  • The ability to turn off auto-updates (and still be able to use the app). I do wonder why I care what's changed if I'm not able to use the app without installing it, and maybe that's an insight into the main development team's thoughts on the users.
  • Show a changelog (or a link to the changelog, a là Brave) before the update begins.
  • To be asked if the update should even download (again, Brave does this better). It may be a desktop client but that still doesn't mean that a) this is a convenient time, or b) that I want to use bandwidth on this.

I could go on but having to look through the git log instead of having a proper changle log is not impressive for a project of this size.

Regards,
iain

@stale
Copy link

stale bot commented Sep 25, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants