alt Hacker NewsLet me be a devil's advocate here: you have essentially two options.
1. You write release notes thet contain technical details. Less than 1% of your customers understand them. More than 90% probably won't even care, let alone understand the document. And then there are the folks who get confused or scared and reach out to customer support with weird questions. This generates extra workload.
2. You explain nothing. The release simply is. The technically minded people are mildly annoyed. A few customers affected by open issues wonder if it's fixed now. The rest of them doesn't even care that there is an uodate and carries on with their lives. Customer service continues to complain about the usual bunch of random and weird customer issues.
It's quite natural to start doing (2) in a consumer facing business, isn't it?
Replies
> It's quite natural to start doing (2) in a consumer facing business, isn't it?
Absolutely.
But also don't break my stuff.
i remember when the TV station would shut down in the middle of the night.
Or businesses would close to do inventory.
We made do.
It would be very simple to write out details but make them harder to access. Motivated users will find them.