问 HN：你如何为多个受众撰写发布说明？
19 分•作者: glidr_dev•5 天前
对于经常发布更新的各位来说，在发布更新时，你们通常会编写一套发布说明，还是会针对不同的受众群体进行改写？
例如：
• 针对开发者的技术版本
• 针对最终用户的简化版本
• 针对利益相关者的更高级别版本，等等…
在我目前的工作岗位上，我见识了各种团队，甚至是目前所在的公司，处理这个问题的方式。
我所见过的：
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.