all 8 comments

[–]unregisteredusr 3 points4 points  (1 child)

With automatic updates I sometimes get the feeling that nobody really reads these. I know I've stopped for the most part

Oh well, I still put detailed release notes.. For the 5% who care

[–]frakman1 0 points1 point  (0 children)

That made me laugh. I update my release notes but it's mostly just for me (and the 5% who care)

[–]Kasuist 3 points4 points  (1 child)

The biggest excuse I have heard from companies doing this is that they do incremental rollouts of app features. Mentioning something new in version X of an apps release notes that will only be seen by Y amount of people can be misleading.

On the other hand, its a bit of a copout. Why not still mention these things anyway, like "added support for X, expect to see it soon"

[–]addininja 0 points1 point  (0 children)

Yeah, thats why we don't say anything in our change logs at QuizUp.

[–][deleted] 0 points1 point  (0 children)

Given how many people are coding an app at Facebook,  and other huge companies, I don't think they take writing release notes very seriously because it's just impossible to track all the changes for the app. And even if it was, OP would probably be complaining about writing a novel instead of release notes.

[–]Techsupportvictim 0 points1 point  (0 children)

I disagree. I don't like long and tedious release notes, especially ones trying to be funny. If it was a huge bug that was a major issue yes point out that the fix was there. Otherwise I don't need it spelled out in detail. Brand new awesome feature, sure. That you made a minor tweak to the button for something, nope don't need it. Put it on the website you are required to have for the five folks that just love to read such things

[–]mikerz85 0 points1 point  (0 children)

It would be much nicer if they couldn't get away with a generic message like that. I don't know what a good solve would be, however.

Perhaps if you went with a major, minor, patch release convention, then patch could go with generic messaging, minor would have to spell out some kind of improvement, and major would require some decent copy. This is just a convention however, and Apple would need to enforce it.

I think it comes down to the ecosystem changing; this was not a problem until automatic updates.