I gotta start writing the hype-oriented 2.6.0 announcement post

Honestly I'm always a bit struggling with which audience those blog posts should have in mind. There's like three types of changelogs I have to write: the point by point changelog included in the source files, the GitHub release changelog, which sysadmins will read to figure out how to upgrade and why to upgrade, and these hype-oriented blog posts.

But if I'm not aiming at sysadmins there, does it mean I should omit writing about admin features, CLI utilities, fixes and all that stuff 🤔

Outline 
@Gargron no update note Mastodon will ever have will beat Dwarf Fortress's "stopped dogs from being depressed because they couldn't figure out how to practice their religion" or "fixed a bug where cats would die from alcohol poisoning if they walked into a tavern"
@Gargron Doesn't this release have the API additions to make saving your place in third party apps viable? If so, that should be in there somewhere to entice/encourage developers.
@Gargron no, don't omit it. it's still important to know "hey btw admins have an easier time now" and maybe some of the popular audience might be interested in admining their own instance down the road. a simple point-by-point of "hey these are some of the new changes that make it easier on admins" is enough.
@Gargron It's okay to hype admins about upgrading.
@Gargron This might like it's coming from left field, but I would target the media. If the end goal is growth then the media can be your biggest ally (or enemy).
Technical notes for developers and sysadmins are critical as well but don't have to be in the big announcement post (and you probably have enough trusted contributors by now that you can start to delegate these).
@Gargron If you want an extra pair of eyes on the rel=me stuff I'm very happy to help. The best writing advice on. release notes is Anna's at Slack: https://slackhq.com/a-little-thing-about-release-notes
A little thing about release notes | The Official Slack Blog

Why they’re important to us, and how we approach the writing of them at Slack

Several People Are Typing
@Gargron Different industry (writing and game design) but have a similar problem. Do consumers care about our behind the scenes stuff? Do Game designers care about our consumer focused stuff? Tricky wicket.