Skip to content

Iteration 1: Write release process documentation for custom packages

In the releases between when we ship our VeraCrypt work in Tails (3.9) and when Tails is based on Buster, we need to maintain the custom packages we create (see #15521 (closed)).

For this we should include a step in the release process to check whether any of the packages we base ours on have an update, and in that case merge the update into our packages.

Feature Branch: feature/15524-veracrypt-release-documentation

Parent Task: #15214 (closed)

Related issues

Original created by @segfault on 15524 (Redmine)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information