I'll usually stop and read them for apps that I like. I like knowing what's changed.
Asklemmy
A loosely moderated place to ask open-ended questions
Search asklemmy π
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
I prefer reading the release notes before updating, because if there was something I don't like often I can't just go back. other then that it would be better if past release notes would be readable in the app, so you can read it later.
I think apps that show the release notes right on next launch just wanted to tick off a feature request the developer did not really find useful to put enough thought into it.
If the app opens it automatically on update, I usually read them. If not then I only go after changelogs for apps I care about and apps that broke.
It depends on how relevant I expect those changes to be to me. For programming languages or libraries I use often for example, I'll always read change logs. For other software, I'll likely only look at it if I'm waiting for a specific bug fix or feature.
Quite the opposite. I don't update my apps at all and only read patch notes to determine whatever to update or not
They're counting on nobody reading them
I donβt use alpha/beta software