问HN：你们是如何为不同受众处理发布说明的？
对于那些经常发布更新的团队来说，您通常是写一套发布说明，还是会为不同的受众重新编写它们？
例如：
• 针对开发者的技术版本
• 针对最终用户的简化版本
• 针对利益相关者的更高层次版本等……
在我目前的职位上，我见过许多不同的团队，甚至是我目前工作的公司在处理这个问题时采取的各种方式。
我看到的情况有：
1. 将原始的GitHub变更日志直接粘贴到客户邮件中（如果您现在这样做，我强烈不推荐）
2. 针对每个受众手动多次重写相同的更新
3. 完全跳过发布说明，因为这工作量太大
所以我想问的是：您或您的公司目前是如何处理多套发布说明的？您觉得是否需要多套发布说明？
我很想听听您有效（或无效）的做法，以及您是否找到过任何可以帮助解决这个问题的工具。
查看原文
For those of you who ship often, when you release updates, do you typically write one set of release notes, or do you end up rewriting them for different audiences?<p>For example:
• technical version for developers
• simplified version for end users
• something more high-level for stakeholders etc…<p>In my current position I’ve seen a plethora of different ways teams, and even the company I currently work for, go about this.<p>What I’ve seen:
1. paste raw GitHub changelogs into customer emails (highly wouldn’t recommend if you’re currently doing this )
2. manually rewrite the same update multiple times for each audience
3. skip release notes entirely because it’s too much work<p>So I guess my question is: How do you or your company currently go about handling more than one set of release notes, and do you feel like more than one set is needed?<p>Would love to hear what’s working (or not working) for you, and if you found any tools that help mitigate this issue.