Ask HN: How do you handle release notes for non-technical users? |
Ask HN: How do you handle release notes for non-technical users? |
What I absolutely hate is the generic release note that seemed to come about with agile release schedules. Notes like, “bug fixes and performance improvements”, “Thanks for using <app_name>, we make regular improvements to ensure your experience is top notch”, or “We update our app often to <insert_marketing_taglines>.”
This tells me nothing and makes me less likely to bother reading any release notes at all.
This will keep existing users on the app for longer. If you're a project manager or manage an app, this is definitely something you should care about.
Also, I'm trying something out here because I saw a loophole, let's see how it goes :)
I use release notes to help me decide whether not to update to the new release. I would prefer that no release note is made at all over that kind of thing. At least that's being honest about not wanting to say what the changes were.