Commit 5551d2aa authored by intrigeri's avatar intrigeri
Browse files

2017-10 report: add my bits.

parent abed5727
......@@ -9,6 +9,22 @@ Code
XXX: List important code work that is not covered already by the Release
section (for example, the changes being worked on for the next version).
- We started evaluating our options regarding a possible
[[!tails_ticket 14789 desc="upgrade to Linux 4.13"]]
in Tails 3.3.
- We had a first sprint to evaluate how it would be like if Tails was
[[based on quarterly snapshots of Debian testing|blueprint/Debian_testing]]:
- We ported most of Tails to Debian Buster.
- We adjusted most of our test suite accordingly.
- We designed a [[!tails_ticket 14791 desc="process"]] and
implemented [[!tails_ticket 14579 desc="tools"]] that will allow
us to tell technical writers what part of the documentation is
affected by changes in our code, test suite, or installed packages.
- We adapted the Debian Security Tracker code to
[[!tails_ticket 14823 desc="track security issues fixed in Debian but not in the snapshots Tails uses"]].
- In November we will check how we are doing and will decide what
the next steps shall be.
Documentation and website
=========================
......@@ -49,6 +65,9 @@ XXX: Ask tails-bugs@boum.org to list hot topics for the last month.
Infrastructure
==============
- We consolidated our system administration team by hiring a new
member. Welcome, groente!
- For our installation of *LimeSurvey*, we implemented an automatic monitoring
of new upstream versions to notify system administrators when a security
update is available ([Git repository](https://git-tails.immerda.ch/monitor-limesurvey-releases)).
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment