summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorsajolida <sajolida@pimienta.org>2019-07-09 09:02:24 +0000
committersajolida <sajolida@pimienta.org>2019-07-09 09:02:24 +0000
commitb816e17b20f99ea159622b927aa6ffa82f2e5b02 (patch)
tree0040e37487ca76ab6f57730ecc8f7636fc81507d
parent26493e9cd462e9c83e3fa9d5a0eb3f46d3052abc (diff)
Document how to tweet about new features several times (Closes: #16681)contrib/16681-tweets-in-the-future
-rw-r--r--wiki/src/contribute/how/documentation/release_notes.mdwn11
1 files changed, 11 insertions, 0 deletions
diff --git a/wiki/src/contribute/how/documentation/release_notes.mdwn b/wiki/src/contribute/how/documentation/release_notes.mdwn
index 6d42c60..8031423 100644
--- a/wiki/src/contribute/how/documentation/release_notes.mdwn
+++ b/wiki/src/contribute/how/documentation/release_notes.mdwn
@@ -79,3 +79,14 @@
- Prepare a tweet with highlights:
- Tails x.y is out: https://tails.boum.org/news/version_x.y/, bla bla bla, and more.
- Add it as a comment to the ticket for the release notes.
+ - If we release new major features ("New features" section), consider
+ scheduling tweets in the future to let the world know about it, even
+ months after we release them.
+ - Write a Tweet, for example:
+ - Did you know?
+ You can xxx in Tails, since $MON (Tails $VERSION).
+ - Add the picture we had in the release notes.
+ - Link to our documentation about the feature.
+ - Create a ticket to tweet about it 3 times in the following 6
+ months, for example once every 2 releases.
+ - Put this ticket on the Technical writing view in Redmine.