docs: keep qa proof out of release tweets · openclaw/openclaw@4593045
steipete
·
2026-05-20
·
via Recent Commits to openclaw:main
File tree
.agents/skills/openclaw-release-maintainer
| Original file line number | Diff line number | Diff line change |
|---|
@@ -170,6 +170,9 @@ live`; keep it clearly beta and avoid implying stable promotion.
|
170 | 170 | CI, validation, or internal release mechanics unless the release is explicitly |
171 | 171 | about those. Peter prefers concrete user wins: features, integrations, |
172 | 172 | workflow improvements, and practical reliability fixes. |
| 173 | +- Do not feature QA parity, test coverage, release gates, or validation lanes in |
| 174 | + user-facing launch tweets. Keep them for release notes or maintainer proof |
| 175 | + unless the operator explicitly asks for validation-focused copy. |
173 | 176 | - Tone: high-signal, slightly cheeky, confident, not corporate. One joke is |
174 | 177 | enough. Avoid punching down, insulting users, or promising what was not |
175 | 178 | verified. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
