summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
author127.0.0.1 <127.0.0.1@web>2018-02-04 11:54:48 +0100
committeramnesia <webmaster@amnesia.boum.org>2018-02-04 11:54:48 +0100
commit8602d42232bf6eaff0d382db4c102e047a22adbd (patch)
treee528302fd5ffdf66dd7dfc097dba9779a19409ba
parentf5921ddade0c7ec8fc789c5d0db55ba7d1a31830 (diff)
better research
-rw-r--r--wiki/src/blueprint/monthly_report/report_2018_01.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/src/blueprint/monthly_report/report_2018_01.mdwn b/wiki/src/blueprint/monthly_report/report_2018_01.mdwn
index 0fe638c..8233ed0 100644
--- a/wiki/src/blueprint/monthly_report/report_2018_01.mdwn
+++ b/wiki/src/blueprint/monthly_report/report_2018_01.mdwn
@@ -95,7 +95,7 @@ than the default"]] This was a hard one, although on the other side we see again
1. [[!tails_ticket 15116 desc="NVidia Maxwell and Pascal graphic cards are still giving problems in Tails 3.5"]]
-1. As every time our Tails signing key updates, many users got scared by the gpg messages received during OpenGPG ISO verification, so we decided to open [[!tails_ticket 14711]] to tell users to update the signing key on verification failure.
+1. As every time our Tails signing key updates, many users got scared by the gpg messages received during OpenGPG ISO verification, but there are several tickets open about this [[!tails_ticket 14711]], [[!tails_ticket 13634]], [[!tails_ticket 14977]]
Strategic planning
==================